{"version":"2.1.307","anchor":"no-proxy-added-to-a-list-of-env-vars-probably-passed-throug","canonical_anchor":"proxy-env-passthrough-excludes-no-proxy","heading":"NO_PROXY moves within the lists of environment variables passed through","tier":"notice","area":"Network","scope":"both","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.307\/e\/no-proxy-added-to-a-list-of-env-vars-probably-passed-throug","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.307","markdown":"### NO_PROXY moves within the lists of environment variables passed through\n\nNO_PROXY is filtered out of the proxy-derived passthrough names and now appears in a separate list alongside SHELL and TRACEPARENT\n\n**Unclear.** It is not clear what this list is used for, so it is not clear how `NO_PROXY` is now treated.\n\n**What**\n\nEnvironment variables are named values set outside Claude Code. `NO_PROXY` lists addresses that should be reached directly rather than through a proxy server. Two changes touch how it is handled:\n\n- An allowlist of environment variables that are passed through now filters `NO_PROXY` out of the names derived from proxy settings.\n\n- `NO_PROXY` appears in a separate list alongside `SHELL`, `TRACEPARENT`, `GIT_CONFIG_NOSYSTEM` and similar variables. What that list is used for was not confirmed.\n\n**Why**\n\nIf you rely on `NO_PROXY` to let some connections skip a proxy, check that it still reaches the commands Claude Code runs, especially where proxy settings are passed through.\n\n- Area: Network\n- Names: `NO_PROXY`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: both\n- Heads-up: yes"}