Follow Discord
Sweep 22 Oct 2026 · 04:32Z Build v2.1.308 527 read Stable v2.1.308 Latest v2.1.308 Next v2.1.308 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.236 ·

Resumed sessions explain why they did not re-arm comment replies on an Artifact

Resuming now says exactly why it did not re-enable automatic comment replies on each Artifact.

You'll notice New Features
JSON All of v2.1.236
You'll noticeTier: how much it should matter to you
3Useful: my rating, 1 to 5
4Signal: worth watching, 1 to 5
ArtifactsArea: what it touches
New FeaturesKind: in v2.1.236,
What probably matters to youSection of the release
What

When you resume a session, Claude Code no longer silently re-enables automatic replies to comments on published Artifacts. It re-arms only what it can, and prints a reason for each one it skipped: you stopped watching it last time, this account cannot publish to that Artifact, another session may already be replying, it could not confirm no other session is replying, or you are already watching the cap of 5 Artifacts at once.

Details
  • At most the most recent Artifact's comment monitor comes back on resume; a summary line names up to two Artifacts that were left unwatched.
  • The skip reasons are internal codes with one sentence each: recorded_stop, not_editor, holder_unknown, held_by_background, watch_cap and watch_cap_reconnect.
  • The watch limit of 5 comes from a constant interpolated into the message, so the sentence always matches the real cap.
  • Re-arming calls are marked as resumes, and an Artifact recorded as armed carries forward the consent to publish replies, so you are not asked again.
Evidence

a resumed session brings back at most its most recent Artifact's comment monitor

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

Feedback