Artifact comment auto-reply subsystem#
Claude can watch artifact comment threads and post replies or edits, off unless you set the env var.
Artifact comment auto-replies sit behind CLAUDE_CODE_ARTIFACT_COMMENTS_AUTOREACT, off by default, with new comments and reply actions.
tengu_sorrel_trellis On for this account, and not off by defaultThe 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
What's wrong with this entry?
A subsystem was added that watches comment threads on artifacts Claude published and, once a human activates Claude on a thread and posts, composes and posts a reply, optionally editing and republishing the artifact. It is switched off in this build unless explicitly enabled.
- Gate order: the environment variable
CLAUDE_CODE_ARTIFACT_COMMENTS_AUTOREACTis read first, otherwise the gatetengu_sorrel_trellis, whose in-source fallback is false, with the real value coming from remote config. - It additionally requires the Artifact tool schema to expose
thread_id. A session-level kill switch permanently disables it once tripped. - The Artifact tool gains
commentsandreplyactions, added to the action enum only when comment verbs are wired, and treated as read-only and concurrency-safe. - Thread scanning uses coalesced and debounced rescans, with per-thread state covering seen comments, its own reply IDs, a breaker, and an hourly cap on turns per artifact. A permission probe runs before acting.
- Live-watch registrations carry
autoReactWiring; background tasks carryautoReactArmedandautoReactSlug; task-notification origins can come fromartifact-auto-react. - When a thread carries edit capability a second composer runs, required to emit one JSON decision object, either
{"action":"reply",...}or an edit carrying the complete new artifact source. The edit is written to a temp file, published through the Artifact tool, attribution is verified with a version echo, and only then is the summary reply posted. - A catalogue of user-facing refusal replies covers pinned versions, inactive edit grants, rate limits, size guards, transient errors and supersession, each stating whether the artifact changed.
- Telemetry is emitted under the event name
artifact_comments_autoreact, with outcomes includingread_failed,breaker_open,stood_down_answered,denied_by_ruleandhourly_cap.
CLAUDE_CODE_ARTIFACT_COMMENTS_AUTOREACT, tengu_sorrel_trellis, I could not apply the requested edit: the artifact is pinned to a fixed version
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.
-
v2.1.227
Auto-reply to artifact comments can include earlier analysis notes
Both mention comment autoreact
-
v2.1.233
Automatic comment replies stand down if someone else answers first
Both mention comment autoreact
-
v2.1.233
Auto-reply guidance tells Claude to check for an existing answer before posting
Both mention comment autoreact