Follow Discord
Sweep 22 Oct 2026 · 04:32Z Build v2.1.308 527 read Stable v2.1.308 Latest v2.1.308 Next v2.1.308 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.307 ·

NO_PROXY moves within the lists of environment variables passed through

NO_PROXY is filtered out of the proxy-derived passthrough names and now appears in a separate list alongside SHELL and TRACEPARENT

Group of 2 You'll notice Internal Changes
JSON All of v2.1.307
You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
NetworkArea: what it touches
Internal ChangesKind: in v2.1.307,
ImprovementsSection of the release

Unclear It is not clear what this list is used for, so it is not clear how NO_PROXY is now treated.

What

Environment 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:

  • An allowlist of environment variables that are passed through now filters NO_PROXY out of the names derived from proxy settings.
  • 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.

Why

If 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.

Read from
Names in the bundleNO_PROXY
How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtIt is not clear what this list is used for, so it is not clear how `NO_PROXY` is now treated.

See this entry in the whole of v2.1.307 →

Feedback