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.234 Home All releases ←olderv2.1.233 v2.1.235newer→
Claude Code v2.1.234

Resuming stopped artifact auto-replies, and marking comments the artifact posted itself

You'll notice
Useful3 Signal4
Artifacts

Comments Claude posts to an artifact are now marked as its own, so it stops replying to itself.

A resume_replies action for re-arming a stopped watch is fully written but unreachable in this build.

Feature flag
tengu_teal_corbel 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: off · compiled default in v2.1.234: on

Read once, for one account on one subscription tier, against v2.1.234. It isn't a statement about your account. What a flag value here can and cannot tell you

What

Artifacts can be watched so Claude replies to their comments automatically, and this build reworks both ends of that loop. Comments now carry a marker saying they were posted through the artifact's own interface, which keeps Claude from treating its own posts as new human input and gives those comments a distinct attribution label. Alongside it sits a resume_replies action for re-arming a watch you stopped, which is fully written but not reachable in this build.

Details
  • Stored comments gained an optional posted_by_artifact boolean, held in memory as postedByArtifact and emitted in comment telemetry as posted_by_artifact: !0; auto-reply arming filters those out before deciding a new human comment has arrived, so Claude no longer answers itself.
  • Two attribution labels, [human, posted by the artifact] and [human, posted by the artifact, sent to you], appear in rendered comments and in the comment-scanning prompt; the transcript label becomes "human, posted by the artifact" instead of plain "human", and everything without the marker keeps its existing attribution.
  • The instructions tell Claude to act on such a comment as that person's request, but to raise it with you if it conflicts with something you typed directly.
  • All of the comment behaviour rides on the artifact comments capability, switched on by the CLAUDE_CODE_ARTIFACT_COMMENTS environment variable or the remote setting tengu_teal_corbel, which defaults to off; without it the labels are never rendered.
  • The resume_replies action re-enables automatic replies after they stopped, whether the live-updates task was killed, the artifact was unwatched, or you interrupted with Ctrl+C. It is offered only inside a branch guarded by a build-time constant that is false here, the same constant that hides watch, unwatch and status, so nothing in this build turns it on.
  • When it does run it asks for approval like a publish, with the always-allow option suppressed so it can never be auto-approved, and prompt copy warning that approving re-arms unattended public replies.
  • Stopping a watch sets a latch, so later publishes or a plain watch return outcome skipped with reason stop_latched rather than quietly re-enabling unattended replies.
  • Refusal reasons surfaced to the model are session_disarmed, remote_session, not_stopped, stale_consent, stop_latched, cancelled, stopped_again and not_enabled; a consent token that no longer matches yields stale_consent, and in remote sessions, keyed off the remote-session environment variable, the action is denied outright with a description saying it is unavailable there and the model told to use watch.
  • The kill-all-agents gesture disarms auto-replies for the whole session and a resume cannot reverse it; only a new session re-arms on publish. Plan mode and Cowork also deny the action because there is no place to ask you.
  • Status output and the connected-artifact list gained an auto_reply field per watch, with text distinguishing "not watching (stopped earlier in this session)" from "auto-replies resumed".
Evidence

Auto-replies are disarmed for this whole session (the kill-all-agents gesture) and a resume cannot reverse that \u2014 a new session re-arms on publish., Claude reports that you asked it to resume automatic comment replies on this artifact, when you asked to resume its comment auto-replies, use the kill-all-agents gesture to disarm auto-replies for the whole session, Auto-replies were NOT resumed: they are disarmed for the whole session (the user's kill-all-agents gesture)., No auto-reply stop is recorded for this artifact in this session, so there is nothing to resume. Nothing here needs approval., approving re-arms unattended public replies, human, posted by the artifact, posted_by_artifact, [human, posted by the artifact, sent to you]

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.234 →