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.242 Home All releases ←olderv2.1.241 v2.1.243newer→
Claude Code v2.1.242

Proxy denial details no longer reach the model

You'll notice
Useful2 Signal2
Sandbox

When a proxy blocks a fetch, only the connect status reaches the model; details go to debug logs.

What

When a network egress proxy blocks an artifact content or asset fetch, the proxy's marker and status detail now go to the debug log, and the message returned to the model keeps only the connect status.

Details
  • Both artifact fetch paths also gained a branch reporting that the relay is unavailable.
Evidence

[artifact] asset fetch: egress proxy denied

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

Related

Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.

See this entry in the whole of v2.1.242 →