Windows: platform plans and manual setup

The Windows goal is also to protect local privacy and make Claude protection status and findings visible. Platform coverage needs its own validation; macOS results cannot establish it.

Preview not released

A Windows version is planned; there is no Windows installer yet (only the macOS version is available). System requirements, signatures, installation steps and actual scope will accompany a release. This page does not assume an available installation flow.

Evidence to look for at release

Item	What needs confirmation
Main programs	Which Claude programs are included and how updates are checked
Child processes	Whether git, node and python are validated; parent coverage does not establish child coverage
Local connections	Tests of loopback rules and local services
Credentials	Which files or system stores are checked and which are outside scope
Private folders	Full isolation is not implemented; selected-file-only access is not established

Strict child-process control is a later design, without a promised release date here. WSL needs separate assessment: control of host Windows processes does not establish coverage inside WSL.

Manual Claude Code configuration available now

These examples are independent of CCIso and do not create file isolation. They have not been connectivity-tested against your proxy environment here.

If your own HTTP proxy listens on local port 8080, run in PowerShell:

$env:HTTPS_PROXY = "http://127.0.0.1:8080"
claude

Use your actual address. This affects programs started afterward from the current PowerShell; do not assume an editor opened from the Start menu reads it. In Claude Code, run /status; the Proxy row should show the configured address.

For settings across sessions, merge the following into %USERPROFILE%\.claude\settings.json, preserving existing fields:

{
  "env": {
    "HTTPS_PROXY": "http://127.0.0.1:8080"
  }
}

Claude Code does not directly support SOCKS proxies. Keep real passwords out of committed project settings. The example address is not a provided proxy.

Handle WSL separately

Claude Code inside WSL uses that environment’s files and settings. Determine a reachable proxy address from inside WSL, then follow Linux manual setup. Do not assume Windows loopback addresses, environment variables or protection status transfer directly.

What a successful check establishes

For manual setup, first confirm that the setting loaded, then that your proxy is reachable. Neither establishes system-level connection rules or private-file isolation. A future CCIso Windows release will also need its own rule, process and credential checks.

Continue with current scope, troubleshooting and downloads. Source: Anthropic’s network configuration, reviewed on November 1, 2026.