Source Intelligence
Follow Discord

DisclaimerUnofficial, and not affiliated with Anthropic. Nearly all of this is read straight out of what ships: npm bundles, captured prompts, published docs. Anthropic's own notes go in verbatim, marked as theirs. The rest is my reading, and every entry carries the strings behind it. If one looks wrong, vote it down and say why.

← All of v2.1.239 Home All releases ←olderv2.1.238 v2.1.240newer→
Claude Code v2.1.239

The new test-network blocker ships switched off

Not switched on
Useful1 Signal3
Testing not in their notes

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

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

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

See this entry in the whole of v2.1.239 →