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

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

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

You'll notice New Features
JSON All of v2.1.247
You'll noticeTier: how much it should matter to you
3Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
PluginsArea: what it touches
New FeaturesKind: in v2.1.247,
New FeaturesSection of the release
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 →

Feedback