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.238 Home All releases ←olderv2.1.237 v2.1.239newer→

Claude Code v2.1.238 20 Aug 2026

Artifact fetches blocked by an egress proxy now say so

You'll notice

Useful3 Signal2

Artifacts

Artifact fetches blocked by your company proxy now say the proxy refused, not just "network error".

What

Fetching artifact JSON, comments or assets now separates a plain network failure from a proxy refusing the CONNECT, reporting json_proxy_refused with the connect status and a message naming the proxy.

Details

Allowlist blocks are routed through a single shared handler.
Only fires when you are behind an egress proxy.

Evidence

json_proxy_refused

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