{"version":"2.1.269","anchor":"artifact-db-writes-gain-optional-optimistic-concurrency-req","canonical_anchor":"artifact-str-replace-writes-gated-behind-a-new-require-versi","heading":"Artifact writes gain optional version-conflict checking","tier":"soon","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269\/e\/artifact-db-writes-gain-optional-optimistic-concurrency-req","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269","markdown":"### Artifact writes gain optional version-conflict checking\n\nArtifact document writes can now ask the server to reject writes that conflict with a newer version, with automatic fallback\n\n**What**\n\n- Artifact database writes (both single writes and batch writes) can now pass a `requireVersion` flag to the server, asking it to reject a write if the artifact has changed since the client last read it.\n\n- Writes made through the `str_replace` editing path also pass `requireVersion`; this only happens when the artifact-DB feature (`CLAUDE_CODE_ARTIFACT_DB`, on by default) is enabled and either the `CLAUDE_CODE_ARTIFACT_DB_STR_REPLACE` environment variable or a remote flag (`tengu_umber_stile`, off by default) is set.\n\n- If a server does not understand `requireVersion`, the client remembers that server as unsupported and automatically retries the write without `requireVersion` instead of failing.\n\n**Why** This adds an opt-in safeguard against silently overwriting someone else's concurrent changes to an artifact, while staying compatible with older servers that don't support the check yet.\n\n- Area: Artifacts\n- Tier: Nothing to try yet\n- Useful: 3\/5\n- Signal: 3\/5"}