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.242 Home All releases ←olderv2.1.241 v2.1.243newer→
Claude Code v2.1.242

Artifact comment replies can move to another session of the same conversation

You'll notice
Useful3 Signal4
Artifacts not in their notes

Automatic replies to Artifact comments can move between sessions of the same conversation.

resume_replies
What

Only one session at a time answers comments on a published Artifact automatically, and that job can now move between sessions of the same conversation. A session that resumes the conversation or republishes the Artifact takes replies from the session currently holding them, the permission dialog says plainly that approving takes replies back from the other session, and both sessions get notices when replies move, come back, or were stopped elsewhere. Claude Code is also told to explain the state to you: the other session answers the comments, no comment notifications arrive in yours meanwhile, and asking to publish or calling resume_replies brings them back. The takeover rides on local session-to-session messaging; with that off it does nothing.

Details
  • The Artifact status output gains a yielded auto-reply state, described as "auto-replies handed to another session of this conversation, which answers the comments now", alongside the existing armed, paused, stopped and disarmed states.
  • A yielded page is retaken by a publish you ask for in this session or by resume_replies; merely asking about the page's status does not take replies back.
  • When replies resume in your session, the notice can say they were "moved here from" the previous session, which "now only watches for new versions".
  • The resume notice for auto-replies gains a third explanation branch, replies "handed to another session of this conversation that resumed it or published there", beside the existing paused-on-interrupt and killed-watch-task cases.
  • The handoff sentence is only produced when the session actually has the comment auto-reply capability, so sessions without it never mention the handoff.
  • Outcomes are counted as took_over_..., takeover_handed_back, takeover_unyield_precautionary, unyield_holder_gone, holder_unreachable and nothing_freed; when local messaging is unavailable the paths return disabled or messaging_off instead.
  • Resume guidance was corrected: rather than promising at most one watch survives --resume or --continue, it now says the most recently published or read Artifact's watch usually returns in an interactive terminal, along with every comment-replying watch, and that other clients may restore nothing.
  • An other_org failure reason joins the existing not_found for Artifacts that cannot be acted on.
  • The older resumed-publish consent wiring around carried Artifact watches, with reasons such as ws_open_error, not_editor and arm_in_flight, was dropped from that call site in favour of a plain catch.
Evidence

unyield_artifact_replies, handed to another session of this conversation that resumed it or published there, auto-replies handed to another session of this conversation, which answers the comments now, auto-replies handed to another session of this conversation

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