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.269 ·

Artifact writes gain optional version-conflict checking

Artifact document writes can now ask the server to reject writes that conflict with a newer version, with automatic fallback

Group of 3 Nothing to try yet Notable No documentation found In Development
JSON All of v2.1.269
Nothing to try yetTier: how much it should matter to you
3Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
ArtifactsArea: what it touches
In DevelopmentKind: in v2.1.269,
What probably matters to youSection of the release

What

  • 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.
  • 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.
  • If a server does not understand requireVersion, the client remembers that server as unsupported and automatically retries the write without requireVersion instead of failing.

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.

Read from
Feature flag
tengu_umber_stile Off by default, switched on for this account

The shipped code defaults this off, and the flag server returned on for the one account this site reads on this version. That is the reading that makes the entry above worth a second look, and it still says nothing about your account.

This account: on · anonymous baseline: on · compiled default in v2.1.269: off

Read once, for one account on one subscription tier, against v2.1.269. It isn't a statement about your account. What a flag value here can and cannot tell you

What has happened since
Flag reading moved The flag server now returns on for tengu_umber_stile, read as this account. A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.
Flag reading moved The flag server now returns off for tengu_umber_stile, read as this account. A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.
Flag reading moved The flag server now returns on for tengu_umber_stile, read as this account. A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.
Flag reading moved The flag server now returns off for tengu_umber_stile, read as this account. A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.
Flag reading moved The flag server now returns on for tengu_umber_stile, read as this account. A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.
Flag reading moved The flag server now returns off for tengu_umber_stile, read as this account. A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.
Flag reading moved The flag server now returns on for tengu_umber_stile, read as this account. A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.
Flag reading moved The flag server now returns off for tengu_umber_stile, read as this account. A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.

See this across every release →

See this entry in the whole of v2.1.269 →

Feedback