Source Intelligence

DisclaimerUnofficial, and not affiliated with Anthropic. Nearly all of this is read straight out of what ships: npm bundles, captured prompts, published docs. Anthropic's own notes go in verbatim, marked as theirs. The rest is my reading, and every entry carries the strings behind it. If one looks wrong, vote it down and say why.

All of v2.1.90 Home All releases olderv2.1.89 v2.1.91newer
Claude Code v2.1.90

Parent Proxy Configuration

What

The sandbox proxy can now route outbound traffic through an upstream (parent) HTTP proxy, enabling use in corporate environments with mandatory egress proxies.

Details
  • Configured via the network.parentProxy setting, with sub-keys for http, https, and noProxy
  • Falls back to standard HTTP_PROXY / HTTPS_PROXY / NO_PROXY environment variables when the setting is not explicitly configured
  • NO_PROXY supports hostname suffixes, wildcard *, and CIDR ranges (both IPv4 and IPv6)
  • Localhost and loopback addresses always bypass the parent proxy
  • CONNECT tunneling through the parent proxy for HTTPS traffic, with proper authentication (Basic auth from proxy URL credentials)
  • Hop-by-hop headers are stripped when forwarding through the proxy
  • Logs configured proxy URLs at startup: Parent proxy configured: http=... https=...
Evidence

Parent proxy routing logic (search for "Upstream HTTP proxy for outbound connections" and "Parent proxy configured")

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

See this entry in the whole of v2.1.90 →