Under the hood
Startup logging now warns when a telemetry destination matches NO_PROXY and will bypass the egress proxy
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
One source agreesOne thing we can check says the same as this entry.
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