Follow Discord
Sweep 22 Oct 2026 · 04:32Z Build v2.1.308 527 read Stable v2.1.308 Latest v2.1.308 Next v2.1.308 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.246 ·

Artifact request failures say when the sandbox proxy blocked them

A blocked network request no longer looks like an artifact permissions problem.

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

A 403 from the sandbox proxy is now recognised and logged separately from a denial by the artifact service itself, so a blocked network egress no longer looks like a permissions problem with the artifact.

Details
  • Failed responses now yield both a human-readable reason and a machine error code taken from the body's error field, restricted to lowercase letters, digits and underscores, up to 64 characters.
Evidence

sandbox proxy denied

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