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

Claude Code v2.1.221 ·

Auto-replies to artifact comments

Claude could answer artifact comments automatically, but the whole path is inert unless you turn it on.

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

Auto-replies to incoming artifact comments sit behind CLAUDE_CODE_ARTIFACT_COMMENTS_AUTOREACT, off by default.

What

The artifact live-updates subscription can be armed to answer incoming comments automatically, but the whole path is inert in this build unless the feature is turned on.

Details
  • gated on CLAUDE_CODE_ARTIFACT_COMMENTS_AUTOREACT, otherwise the gate "tengu_sorrel_trellis" whose fallback is false; it also requires the comment schema to expose "thread_id"
  • when armed, websocket frames of kind "comment" go to an auto-reply routine instead of becoming a stale-version notice
  • tasks carry autoReactArmed and autoReactSlug state
  • killing the live-updates task disarms auto-replies for that artifact and posts a disclosure task-notification; a later publish re-arms them and notifies the model
Evidence

Do not republish to re-enable auto-replies unless the user asks.

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

Read from
Feature flag
tengu_sorrel_trellis 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.221: off

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.221. 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_sorrel_trellis, 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_sorrel_trellis, 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_sorrel_trellis, 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_sorrel_trellis, 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: CLAUDE_CODE_ARTIFACT_COMMENTS_AUTOREACT

See this entry in the whole of v2.1.221 →

Feedback