Source Intelligence

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

Egress-proxy refusals on artifact fetches are named as such

You'll notice
Useful2 Signal2
Artifacts

An artifact fetch blocked by your corporate proxy now says so instead of looking like a service failure.

What

An artifact content fetch blocked by a corporate egress proxy now reports its own reason code and an error naming the proxy's CONNECT status, rather than a generic relay failure, so a network policy problem is distinguishable from a service problem.

Details
  • A separate message explains that asset reads work only locally or from a cloud session with the gateway relay enabled.
Evidence

artifact content fetch refused by the environment's egress proxy

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.242 →