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.248entry #273

Claude Code v2.1.248 ·

Artifact writes can skip a re-read when your own last read saw the current version

Publishing an artifact skips its re-read check when your last read matched the live version.

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

Publishing an artifact normally re-reads the live page to check nobody else changed it. That round trip is now skipped when the publish is your own and your recorded read already matched the live version with no other observers. On by default; a server override can turn it off.

Details
  • Gated on tengu_cobalt_plinth_teasel, whose compiled fallback is on.
  • The skip path returns reason: "proceed_own_version" and emits artifact_guard_autoread with mode: proceed_own_version.
Evidence

tengu_cobalt_plinth_teasel

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

Read from
Feature flag
tengu_cobalt_plinth_teasel Not enough to say

Nothing here resolved what this flag was doing on this version, so nothing here should be read as on or off.

This account: no value returned · anonymous baseline: no value returned · compiled default in v2.1.248: on

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

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_teasel

See this entry in the whole of v2.1.248 →

Feedback