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

Claude Code v2.1.238 ·

Clearer reasons when auto-replies cannot be resumed

Auto-reply resume failures now say whether arming is still in progress or watch state was incomplete.

You'll notice Improvements
JSON All of v2.1.238
You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
ArtifactsArea: what it touches
ImprovementsKind: in v2.1.238,
ImprovementsSection of the release
What

Resuming automatic replies to artifact comments now reports two specific outcomes that previously fell through to vaguer ones: arming is still in progress, in which case /tasks will show whether it came back, and the conversation's saved watch state was incomplete.

Details
  • The "not stopped" message now also explains that a pause caused by an interrupt lifts on the user's next message.
Evidence

are still starting up; /tasks will show whether they came back.

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

Read from
Names in the bundle/tasks
Since it was published

The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.

Confirmed since Anthropic's documentation has since written up /tasks, on Explore the .claude directory. | `~/.claude/tasks/` | Task lists that a resumed session would pick up | claude-directory see the edit
How sure we are
One source agreesOne thing we can check says the same as this entry.
Anthropic's documentation agreesAnthropic's documentation has since written up /tasks, on Explore the .claude directory.

See this entry in the whole of v2.1.238 →

Feedback