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.238 Home All releases ←olderv2.1.237 v2.1.239newer→
Claude Code v2.1.238

Resuming an already-running subagent now fails loudly

You'll notice
Useful3 Signal2
Subagents

Resuming a subagent that is already running now errors instead of starting a duplicate.

What

Asking to resume a subagent that is already running, or already mid-resume, throws instead of quietly starting a second copy. Completion, failure and kill each now publish a settled event, flagging whether messages were left stranded.

Details
  • Failures reading the state a resume needs are classified, so a transient read error surfaces as its own error type rather than a generic failure.
Evidence

is already running or being resumed

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