Follow Discord
Sweep 10 Nov 2026 · 02:18Z Build v2.1.322 539 read Stable v2.1.311 Latest v2.1.322 Next v2.1.322 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.265 ·

New artifact database error kinds surfaced verbatim

Artifact database now reports specific edit-conflict errors instead of a generic failure

You'll notice Improvements
JSON All of v2.1.265
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.265,
ImprovementsSection of the release
What

When Claude Code's artifact database rejects an edit, it now passes through several specific error reasons instead of collapsing them into a generic failure: edit_no_match, edit_ambiguous, edit_field_missing, edit_field_not_string, and version_mismatch.

Why

This makes it clearer why an edit to an artifact failed, for example because the text to replace couldn't be found, matched more than one place, or the artifact had been changed by someone else in the meantime, rather than just showing an unhelpful generic error.

Read from
Names in the bundleedit_no_matchedit_ambiguousversion_mismatch
What the documentation says
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 version_mismatch, on Agent SDK reference - TypeScript. | "protocol_version_mismatch" agent-sdk/typescript 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 version_mismatch, on Agent SDK reference - TypeScript.

See this entry in the whole of v2.1.265 →

Feedback