{"version":"2.1.265","anchor":"new-artifact-database-error-kinds-surfaced-verbatim","canonical_anchor":"new-artifact-database-error-kinds-surfaced-verbatim","heading":"New artifact database error kinds surfaced verbatim","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265\/e\/new-artifact-database-error-kinds-surfaced-verbatim","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265","markdown":"### New artifact database error kinds surfaced verbatim\n\nArtifact database now reports specific edit-conflict errors instead of a generic failure\n\n**What**\n\nWhen 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`.\n\n**Why**\n\nThis 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.\n\n- Area: Artifacts\n- Names: `edit_no_match`, `edit_ambiguous`, `version_mismatch`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}