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.247 Home All releases ←olderv2.1.246 v2.1.248newer→
Claude Code v2.1.247

Shell commands started by the main turn survive a plugin turn abort

You'll notice
Useful3 Signal2
Plugins

A shell command keeps running in the background when a plugin aborts the turn that started it.

What

When a plugin aborts the current turn (the model sees [Request interrupted by a plugin for tool use]), a shell command started by that turn is no longer killed and is no longer refused at spawn time. It keeps running in the background instead. This is live for everyone on this build and only applies to that one abort reason.

Details
  • Shell calls are now tagged with who started them: inner, turn or agent. Only turn calls get the survive-the-abort treatment.
  • The per-call opt-in is computed at the Bash and PowerShell call sites and is true only when backgrounding is not otherwise forbidden and the command parses as a simple, non-interactive command line.
  • Interactive or compound command lines are still terminated on abort, as before.
  • No flag controls this; the two helpers behind it did not exist in 2.1.246.
Evidence

turnAbortBackgrounds

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