Follow Discord
Sweep 29 Sep 2026 · 18:10Z Build v2.1.285 506 read Stable v2.1.280 Latest v2.1.285 Next v2.1.285 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.285 ·

Artifact publishing retries more reliably and reports when it merged over a newer version

Artifact publish retries honour retry-after with jitter and retry relay outages, and the result now warns when it merged over a newer version

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

What

Artifacts are files Claude Code publishes so they can be viewed or shared. This release changes how publishing works:

  • Retries now wait according to the server's retry-after hint plus a small random delay, and a relay-unavailable response also triggers a retry. Before, the delay only came from retry-after, with a cap.
  • Claude Code now keeps track of its own version and any merged version of a publish.
  • A publish response can include merged_over, which describes the base version, the live version, and the files that were changed or left out.
  • When a publish was merged over a newer version, the result shown to Claude now says so, lists the changed and removed files, and tells it to re-read them before editing.
  • File reads now include a title, and the relay request can ask for compression with a compress option.

Why

Publishing should fail less often during brief server outages. The merged-over note stops Claude from overwriting files that changed elsewhere, because it is told to read the newer content first.

How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtWhat a merged version means for the artifact a reader sees is not settled.

See this entry in the whole of v2.1.285 →

Feedback