What
When Claude Code starts up, it now checks each configured telemetry forwarding destination against the NO_PROXY environment variable. If the egress-boundary proxy mode is active and a destination's URL matches NO_PROXY, it logs a message noting that exports to that host will skip the proxy.
Why
This helps administrators notice when telemetry data is bypassing an intended network proxy, which matters for environments that route all outbound traffic through a controlled egress point.
Names in the bundleNO_PROXY
The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.
Added since
A small documentation edit on Use Claude Science on a corporate network touched a line naming NO_PROXY after this was published.
* On macOS, the Claude Science app reads a file named `env` in its data folder (`~/.claude-science/env` unless you moved the data folder) when it launches. The file holds `KEY=VALUE` lines (`export KEY=VALUE` also works). Put the three var…claude-science/corporate-networks see the edit
Confirmed since
Anthropic's documentation has since written up NO_PROXY, on Claude apps gateway for Amazon Bedrock, Claude Platform on AWS, Google Cloud, and Microsoft Foundry.
| Private-network address | At `/login`, Claude Code requires the gateway's hostname or IP address to resolve only to private addresses: RFC 1918, link-local, CGNAT `100.64.0.0/10`, IPv6 ULA `fc00::/7`, or loopback. For a gateway you host,…claude-apps-gateway see the edit
Two sources agreeTwo things we can check say the same as this entry.
Anthropic's documentation agrees
Anthropic's documentation has since written up NO_PROXY, on Claude apps gateway for Amazon Bedrock, Claude Platform on AWS, Google Cloud…
Anthropic's release notes agree
Fixed the Claude apps gateway's telemetry relay ignoring a collector hostname or domain listed in NO_PROXY when a proxy is set