{"version":"2.1.265","anchor":"new-artifact-document-versioning-guidance-text","canonical_anchor":"new-artifact-document-versioning-guidance-text","heading":"New artifact document versioning guidance text","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265\/e\/new-artifact-document-versioning-guidance-text","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265","markdown":"### New artifact document versioning guidance text\n\nNew guidance text explains how to safely update artifact documents using version numbers\n\n**What**\n\nClaude Code has new built-in guidance explaining how to edit \"artifact\" documents safely when multiple edits might happen. Every time a document is read or written, the response includes a version number. To update the document with `update` or `str_replace`, that version must be passed back as `if_version`. If the document has changed since that version was read, the write is refused and nothing is applied.\n\n**Why**\n\nThis prevents one edit from silently overwriting changes made in between, since a write only succeeds if it's based on the document's current version.\n\n- Area: Artifacts\n- Names: `if_version`\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}