Network proxy changedthird-party/claude-desktop/network-proxy
Nearest release: v2.1.319, published 6 hours after upstream edited the page. Shown because the two are within 24 hours of each other. Nothing here says the release caused the edit.
Upstream edited this page at 5 Nov 2026 18:33 UTC, give or take a minute or two: the time comes from Anthropic’s own sitemap rather than from a commit. This site recorded the change at 5 Nov 2026 18:37 UTC.
Upstream edited
Recorded here
Lines+5added
Lines−1removed
From line
23
where the diff opens
First seen
2 Sep 2026
this site's first read of the page
Recorded edits18to this page, all time
The whole hunk
from line 23, old and new numbered
/
from line 23
2323A few limits apply to the agent regardless of how the proxy is chosen:
2424
2525* Only `http://` and `https://` proxies are handed to the agent. If the OS or PAC answer is a SOCKS proxy, the app skips it, and the agent connects directly or through the last `http://` or `https://` proxy named for the inference endpoint since Claude Desktop started.
26* There is no interactive proxy sign-in. If your proxy requires a username and password, neither the app nor the agent can prompt for them and requests fail. Run a local forwarding proxy that authenticates upstream on the device (for example, Cntlm or Px) and point the OS or the pinned key at it.
26* There is no interactive proxy sign-in. If your proxy requires a username and password, neither the app, the agent, nor the built-in GitHub connector's server can prompt for them and requests fail. The connector's server gets the proxy's address and no credential, so a proxy that signs devices in with NTLM or Kerberos refuses it too. Run a local forwarding proxy that authenticates upstream on the device (for example, Cntlm or Px) and point the OS or the pinned key at it.
2727* If your proxy intercepts TLS, see [TLS-intercepting proxies](#tls-intercepting-proxies) below.
2828
2929### PAC script for the sandboxed shell
from line 83
8383| Web Fetch in Chat and Cowork sessions, and remote managed MCP servers | App proxy (the app makes these connections) |
8484| Local (`stdio`) servers in [`managedMcpServers`](https://claude.com/docs/third-party/claude-desktop/configuration#managedmcpservers) | The app gives the server no proxy variables. Set `HTTPS_PROXY` in the entry's `env`, or have its `envHelper` script print it. In the admin console, use the **Environment helper script** field. |
8585| Sync of the plugin marketplaces you configure, and `aws` CLI calls the app makes for Bedrock sign-in | App proxy, resolved for the specific host |
86| The built-in [GitHub connector](https://claude.com/docs/third-party/claude-desktop/connectors-github.md#local-connector)'s calls to GitHub | App proxy, resolved for the host that serves the GitHub API (`api.github.com`, `api.<tenant>.ghe.com` for a tenant on `ghe.com`, or your GitHub Enterprise Server instance's own host) when the app starts the connector's server, such as at launch or after a sign-in. If the answer names only SOCKS proxies, the server connects directly. |
8687| Cowork sandbox download from `downloads.claude.ai` | App proxy |
8788| Telemetry and crash reports to Anthropic, if enabled | App proxy |
8889| OpenTelemetry export to your collector | App proxy for the app's own events; the same single proxy as inference for Claude Code metrics and logs |
from line 189
188189* **Last proxy reused**: a `Keeping system proxy` line, when the OS answer was direct, SOCKS, or missing
189190* **SOCKS answer from the OS**: a `Skipping SOCKS proxy entry` line
190191* **Proxy variables from Claude Code managed settings**: a line that names the variables set or replaced, and the settings file they came from
192* **Proxy handed to the built-in GitHub connector**: a `[github-mcp] bundled server connected` line that lists `HTTPS_PROXY` under `envKeys`
191193
192194For Cowork's sandboxed shell, open `cowork_vm_node.log` in the same directory and look for these lines:
193195
from line 199
197199**Agent connects directly while the app is proxied.** The OS or PAC answer for the inference endpoint was `DIRECT` or SOCKS-only. Adjust the PAC rule for the inference host, or pin `egressProxyUrl`.
198200
199201**New sessions keep using a proxy after the device leaves its network.** Once the app has been given a proxy for the inference endpoint, it keeps handing that proxy to new sessions while the OS or PAC answer is a direct connection, a SOCKS proxy, or no answer. Quit and reopen Claude Desktop.
202
203**The built-in GitHub connector's tools fail after the device changes networks.** The connector's server keeps the proxy that the app resolved when the server started. Quit and reopen Claude Desktop.
200204
201205**Cowork's sandboxed shell has no proxy on macOS while the app is proxied.** Check the PAC address in the OS proxy settings. The sandboxed shell uses its own copy of the PAC script. macOS refuses the download of that copy from a plain `http://` address unless the host is one of the exceptions listed under [PAC script for the sandboxed shell](#pac-script-for-the-sandboxed-shell). The app's logs then record `PAC fetch from … refused: macOS requires https for this address (App Transport Security)`, which you can search for in the [logs directory](https://claude.com/docs/third-party/claude-desktop/data-storage.md). Serve the script over `https://`.
202206
No line in this hunk matches that.