Follow Discord
Sweep 25 Sep 2026 · 19:33Z Build v2.1.283 504 read Stable v2.1.274 Latest v2.1.283 Next v2.1.283 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.280 ·

Artifact database writes can now carry a request_id for safer retries

Artifact database writes can now include a request_id so retries after a failure aren't duplicated

Under the hood Improvements
JSON All of v2.1.280
Under the hoodTier: 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.280,
ImprovementsSection of the release
What

When Claude Code writes to the artifact database (both single and batch writes), it can now attach a request_id to the request so the server can recognize if the same request was already received, for example after a retry. If the server says it doesn't support the request_id field, Claude Code removes it and retries once, then remembers that refusal for a cooldown period so it doesn't keep sending a field the server will reject.

Why

This makes retried artifact writes safer by letting the server tell duplicate requests apart from new ones, while avoiding wasted retries against servers that don't support the feature.

Read from
Names in the bundlerequest_id
Since it was published

The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.

Confirmed since Anthropic's documentation has since written up request_id, on Compliance API. - `request_id: string` api/compliance see the edit
How sure we are
One source agreesOne thing we can check says the same as this entry.
Anthropic's documentation agreesAnthropic's documentation has since written up request_id, on Compliance API.

See this entry in the whole of v2.1.280 →

Feedback