Follow Discord
Sweep 22 Oct 2026 · 04:32Z Build v2.1.308 527 read Stable v2.1.308 Latest v2.1.308 Next v2.1.308 Feeds RSS JSON llms.txt llms-full.txt Unofficial
HomeReleasesv2.1.227entry #97

Claude Code v2.1.227 ·

Republishing a stale artifact can now pull in the current version for you

Publishing over a stale artifact now fetches the current version so Claude can merge and retry.

You'll notice New Features
JSON All of v2.1.227
You'll noticeTier: how much it should matter to you
3Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
ArtifactsArea: what it touches
New FeaturesKind: in v2.1.227,
New FeaturesSection of the release
What

Previously a publish was refused when your session had not seen the latest version of a page you were about to overwrite. Claude can now fetch the live page itself, count it as viewed, and hand it back inline with instructions to merge your changes and republish. It applies only to pages you own that nobody else is co-writing, and only under a size cap and a read timeout.

Details
  • Controlled by tengu_cobalt_plinth_moss, which falls back to on when no remote value is present.
  • A successful auto-read raises stale_version_guard_seeded; the page is returned in full for you to merge.
  • Refusals are logged under artifact_guard_autoread with a reason: gate_off, over_cap, read_timeout or sibling_in_flight.
  • Pages containing control bytes are rejected rather than read.
Evidence

artifact_guard_autoread

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

Read from
Feature flag
tengu_cobalt_plinth_moss On for this account, and not off by default

The flag server returned on for the one account this site reads, and nothing in this release compiles it off by default. The compiled default is shown below, and says which it is when we cannot read one: a fifth of gates compile in a string or a number rather than on or off, and most published releases have no gate table behind them at all. No client can see what the server returns for your account.

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

These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.

Read once, for one account on one subscription tier, against v2.1.227. 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_cobalt_plinth_moss, 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 nothing at all, having stopped carrying it for tengu_cobalt_plinth_moss, 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 →

How sure we are
One source agreesOne thing we can check says the same as this entry.
The name it cites is new in this buildNew in this build: tengu_cobalt_plinth_moss

See this entry in the whole of v2.1.227 →

Feedback