Source Intelligence
Follow Discord

DisclaimerUnofficial, and not affiliated with Anthropic. Nearly all of this is read straight out of what ships: npm bundles, captured prompts, published docs. Anthropic's own notes go in verbatim, marked as theirs. The rest is my reading, and every entry carries the strings behind it. If one looks wrong, vote it down and say why.

← All of v2.1.248 Home All releases ←olderv2.1.247 v2.1.250newer→
Claude Code v2.1.248

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

You'll notice
Useful2 Signal2
Artifacts

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

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: off

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

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.

See this entry in the whole of v2.1.248 →