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.221 Home All releases ←olderv2.1.220 v2.1.222newer→
Claude Code v2.1.221

Auto-replies to artifact comments

Not switched on
Useful3 Signal5
Artifacts Notable not in their notes

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

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

Feature flag
tengu_sorrel_trellis 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.221: 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.221. It isn't a statement about your account. What a flag value here can and cannot tell you

CLAUDE_CODE_ARTIFACT_COMMENTS_AUTOREACT
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.

Related

Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.

See this entry in the whole of v2.1.221 →