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
HomeReleasesv2.1.239entry #293

Claude Code v2.1.239 ·

Test runs are refused real network access

Code running under a test runtime cannot make live network calls unless an opt-in variable is set.

Under the hood No documentation found Internal Changes
JSON All of v2.1.239
Under the hoodTier: how much it should matter to you
1Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
InternalsArea: what it touches
Internal ChangesKind: in v2.1.239,
Internal ChangesSection of the release
What

The HTTP layer now blocks live requests made from a test runtime unless an opt-in environment variable is set. Developer-facing only; nothing changes for normal CLI use.

Details
  • Every request URL is classified as loopback, opted-in or refused. Loopback is always allowed.
  • Real access requires CLAUDE_CODE_TEST_ALLOW_REAL_NETWORK=1, which also prints a stderr notice on each live request.
  • Refused requests raise a dedicated egress error; redirects are re-checked against the same rules.
  • Separate messages cover the blocked case and a missing recorded fixture, each telling the developer how to record one.
Evidence

Run the file via bun run test:file -- <path> with this request mocked, or set CLAUDE_CODE_TEST_ALLOW_REAL_NETWORK=1 for an intentional live probe., test runtimes must not reach the network

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

Read from
Names in the bundleCLAUDE_CODE_TEST_ALLOW_REAL_NETWORK
How sure we are
One source agreesOne thing we can check says the same as this entry.
The name it cites is new in this buildNew in this build: CLAUDE_CODE_TEST_ALLOW_REAL_NETWORK

See this entry in the whole of v2.1.239 →

Feedback