Where TokenScope works today
Supported platforms, environments, and network configurations — with clear labeling for planned and unsupported items.
Last reviewed: July 2026
Status legend
Operating system
| Item | Status | Notes |
|---|---|---|
| Windows 10 / 11 | Supported | Native launcher (.exe). No runtime required. |
| macOS | Planned | macOS launcher is in progress. Developers on macOS can be onboarded when it is available. |
| Linux | Planned | Linux launcher is in progress alongside the macOS release. |
| Windows Subsystem for Linux | Planned | WSL support is planned as part of the Linux launcher release. |
Claude tooling
| Item | Status | Notes |
|---|---|---|
| Claude Code | Supported | Primary supported interface. Launcher sets proxy environment variables automatically. |
| Claude desktop application | Not currently supported | Desktop application proxy configuration is not currently supported. |
| IDE-embedded terminals | Supported with configuration | Claude Code launched from a terminal inside VS Code or similar IDE works with the launcher active. |
Development environment
| Item | Status | Notes |
|---|---|---|
| Remote development (SSH) | Planned | Remote environment support is on the roadmap. |
| Dev containers | Planned | Dev container and Codespaces support is on the roadmap. |
| Docker workloads | Not currently supported | Claude Code is not typically used inside Docker. Server-side API proxy support is on the roadmap. |
| CI/CD pipelines | Planned | Direct API integration without the launcher is on the roadmap. |
| Server-side Anthropic API workloads | Planned | API proxy integration without the launcher is planned. |
Network
| Item | Status | Notes |
|---|---|---|
| Corporate HTTP proxy | Supported with configuration | Standard HTTP_PROXY and HTTPS_PROXY environment variables are respected. Administrator setup may be required. |
| Enterprise firewalls | Supported with configuration | Outbound HTTPS to the TokenScope proxy endpoint must be permitted. Contact support for the required allow-list. |
| VPN environments | Supported with configuration | Split-tunnel and full-tunnel VPN configurations are generally supported. Network-specific routing may require IT configuration. |
Integration types
TokenScope supports different integration types depending on the workload. The Claude Code launcher is the primary supported integration today.
| Integration | Typical use | Code changes | Admin setup | Status |
|---|---|---|---|---|
| Claude Code launcher | Individual developer use on Windows | No | Minimal | Supported |
| Managed team rollout | Engineering organization deployment | No application code change | Yes | Supported |
| API proxy | Backend or server-side workloads | Configuration-dependent | Yes | Planned |
| SDK integration | Custom application development | Possible | Yes | Planned |
API proxy and SDK integrations are on the roadmap. Contact us to discuss your server-side use case.
Minimum requirements
Developer machine
- Windows 10 version 1903 or later (Windows 11 recommended)
- Claude Code — latest version recommended
- A modern browser for authentication (Chrome, Firefox, Edge, Safari)
- Outbound HTTPS access to the TokenScope proxy
Network
- Outbound HTTPS (port 443) to the TokenScope proxy endpoint
- Standard HTTP proxy variables respected (HTTP_PROXY, HTTPS_PROXY)
- No inbound ports required on developer machines
For enterprise firewall allow-list requirements, email hello@aitokenscope.com.
Enterprise network environments
Outbound HTTPS to the TokenScope proxy endpoint must be permitted through enterprise firewalls and proxy servers. Split-tunnel and full-tunnel VPN configurations are generally supported with standard proxy environment variable configuration. Contact us for specific IP ranges and allow-list information before deploying to a restricted network.
macOS and Linux
The TokenScope launcher is currently available for Windows only. macOS and Linux launcher support is in progress. If your team uses macOS or Linux, contact us to be notified when those launchers are available.
Questions about your environment?
Contact us to discuss network requirements, planned macOS or Linux deployment, or server-side integration options.