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.234 ·

Artifact read-back and database writes report unknown outcomes instead of failures

A failed artifact request inside the cloud relay now reports an unknown outcome so Claude re-reads before retrying.

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

When a request to the artifact service fails inside the cloud relay, Claude is now told the outcome is unknown and to re-read before retrying, rather than being told the operation failed. That stops it repeating a write that may already have applied.

Details
  • Failures on the relay path are reported as relay_request_error instead of request_error.
  • Retry-after handling now applies only to a genuine 429 from the artifact service, not to a relay response.
  • The read-back and publish calls dropped their per-call host, auth and status-validation options.
  • New telemetry for repairing nested HTML: nested_repair_depth_cap and nested_repair_miss.
Evidence

db write outcome unknown (relay request failed) — it may have applied; read back before retrying, read-back relay HTTP

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

Feedback