Auto-reply arming via the watch action, its consent state and prompt changes are all present but not enabled by default.
Unattended replies to comments on an artifact could previously be armed only by publishing it. The watch action can now arm them too, on an artifact you can edit whose link you gave in your own message, and the tool result explains which of those conditions failed when it cannot. The code paths, the per-artifact consent state and the changed permission prompt are all present in this build, but nothing in it turns the capability on by default.
- The whole auto-reply capability stays off unless the environment variable
CLAUDE_CODE_ARTIFACT_COMMENTS_AUTOREACTis set or the server-side feature switch namedtengu_sorrel_trellisis enabled by config; the value shipped in the build is off. - Auto-replies never arm on an artifact you can only view, and never on one whose link you did not supply yourself in the message that started the turn.
- When a watch does arm a subscription and the resulting task reports no auto-reply, the result carries the specific reason as fields:
can_edit: !1for an account that cannot edit the artifact,user_turn: !1when no message from you started the turn,named_by_user: !1when the link did not come from your own message, andreplies_declined: !0when you declined auto-replies earlier in the session. - That reason ladder is computed only when the tool schema exposes comment verbs and the session's auto-react check passes, which requires that you have not disarmed auto-react; cloud sessions return earlier and never reach it.
- Approval is now asked once per artifact and separately from watching, so an existing approval to watch no longer covers a watch that would also let Claude answer comments unattended.
- New per-artifact state records whether that consent is outstanding, approved or declined, and which artifacts you are not an editor of, and surrounding prose now mentions comment wakes in cloud sessions only conditionally.
unattended_turn, auto-replies arm only when the user asks for the watch in their own message, and no message from the user started this turn, asked once per artifact, as a publish is, never on one the user can only view
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
tengu_sorrel_trellis Off by default, switched on for this accountThe 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.246: off
Read once, for one account on one subscription tier, against v2.1.246. It isn't a statement about your account. What a flag value here can and cannot tell you
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.
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.
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.
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.