Source Intelligence
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.234 Home All releases ←olderv2.1.233 v2.1.235newer→
Claude Code v2.1.234

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

You'll notice
Useful3 Signal3
Artifacts

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

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 →