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

Claude Code v2.1.246 ·

Blocked artifact content fetches say whether the block is temporary

A proxy-blocked artifact fetch now says whether it's a temporary scan outage or a permanent block.

You'll notice Improvements
JSON All of v2.1.246
You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
ArtifactsArea: what it touches
ImprovementsKind: in v2.1.246,
ImprovementsSection of the release
What

When the sandbox proxy blocks a fetch of artifact content with HTTP 403, the failure is now sorted into a temporary scan outage versus a permanent block, each with its own explanation, so the model knows whether to retry.

Details
  • A 403 whose reason ends in "(fail closed)" is treated as transient; other content-scan blocks are treated as permanent.
  • A separate message covers proxy denials that are not content-scan related.
Evidence

artifact content fetch blocked: the sandbox proxy's content scan was unavailable (HTTP 403). This is transient; retry.

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

Feedback