{"version":"2.1.277","anchor":"no-proxy-aware-telemetry-relay-warning","canonical_anchor":"no-proxy-aware-telemetry-relay-warning","heading":"NO_PROXY-aware telemetry relay warning","tier":"internal","area":"Telemetry","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.277\/e\/no-proxy-aware-telemetry-relay-warning","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.277","markdown":"### NO_PROXY-aware telemetry relay warning\n\nStartup logging now warns when a telemetry destination matches NO_PROXY and will bypass the egress proxy\n\n**What**\n\nWhen 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.\n\n**Why**\n\nThis 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.\n\n- Area: Telemetry\n- Names: `NO_PROXY`\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}