Follow Discord
Sweep 22 Oct 2026 · 21:04Z Build v2.1.309 528 read Stable v2.1.308 Latest v2.1.309 Next v2.1.309 Feeds RSS JSON llms.txt llms-full.txt Unofficial
HomeReleasesv2.1.239entry #243

Claude Code v2.1.239 ·

The new test-network blocker ships switched off

A module that blocks network access during test runs ships complete but does nothing here.

Nothing to try yet No documentation found In Development
JSON All of v2.1.239
Nothing to try yetTier: how much it should matter to you
1Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
TestingArea: what it touches
In DevelopmentKind: in v2.1.239,
In DevelopmentSection of the release

The test-network blocker's arming check is compiled to false and its installer has no caller.

What

The module that stops test runs from reaching the network is present in full but does nothing in this build: the check that arms it is compiled to a constant false, so the request-layer hooks return immediately, and the interceptor installer has no caller anywhere in the bundle.

Details
  • Blocked requests would report "Blocked under test: ... test runtimes must not reach the network", with the remedy of setting CLAUDE_CODE_TEST_ALLOW_REAL_NETWORK=1 for an intentional live probe.
  • Includes a dedicated error type carrying the code TestEgressBlocked, redirect-following checks, and a loopback exemption that applies regardless.
  • Related change that is live: test fixture helpers now report a shared "Fixture missing" message rather than checking CI and record-mode variables themselves.
Evidence

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