Follow Discord
Sweep 22 Sep 2026 · 17:19Z Build v2.1.280 501 read Stable v2.1.267 Latest v2.1.280 Next v2.1.280 Feeds RSS JSON llms.txt Unofficial
Claude Code v2.1.267 ·

Artifact hot-update mechanism gets its own flag and deadline/seq schema fields

← All of v2.1.267 Home All releases

Artifact hot-update/live-doc syncing now has its own feature flag and new deadline, seq, and unchanged fields

TierUnder the hoodhow much it should matter to you
Useful2my rating, 1 to 5
Signal3worth watching, 1 to 5
AreaArtifactswhat it touches
KindInternal Changesin v2.1.267,
Group of 3 Under the hood No documentation found

Artifact hot-update/live-doc syncing now has its own feature flag and new deadline, seq, and unchanged fields

What

  • The artifact hot-update (live-reload) check now uses its own CLAUDE_CODE_ARTIFACT_HOT environment variable and tengu_copper_hinge_wren gate, instead of incorrectly sharing the CLAUDE_CODE_ARTIFACT_TYPES variable and tengu_cobalt_plinth_larch gate used by the separate artifact-types feature.
  • Artifact publish requests can now pass a deadline field, which is forwarded to the create/update/live-doc publish calls; the publish response can echo back deadline plus a deadlineDropped flag, along with new seq and unchanged fields.
  • The artifact/live-doc read response schema gains seq and unchanged fields, and (only when a feature gate is on) deadline/deadlineDropped fields, supporting a long-poll style read.

Why

Separating the hot-update flag from the unrelated artifact-types flag means each can be turned on or off independently without accidental interference. The new deadline/seq/unchanged fields lay the groundwork for telling older open copies of a published artifact when to stop and for tracking whether a read actually changed.

Read from
Names in the bundleCLAUDE_CODE_ARTIFACT_HOT
Feature flag
tengu_copper_hinge_wren 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.267: off

tengu_cobalt_plinth_larch Off in both readings

The flag server returned off for the account this site reads and for the anonymous baseline. A reading of off cannot rule out a rollout these two readings sit outside of.

This account: off · anonymous baseline: off · compiled default in v2.1.267: not a boolean we can read

Read once, for one account on one subscription tier, against v2.1.267. 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: CLAUDE_CODE_ARTIFACT_HOT

See this entry in the whole of v2.1.267 →

Feedback