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
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 sinceAnthropic's documentation has since written up version_mismatch, on Agent SDK reference - TypeScript.| "protocol_version_mismatch"agent-sdk/typescriptsee 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.