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

Claude Code v2.1.251 ·

Backgrounded commands record whether the move was to deliver a queued message

Backgrounded commands now record whether they moved aside to deliver a queued message.

Under the hood Internal Changes
JSON All of v2.1.251
Under the hoodTier: how much it should matter to you
1Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
BashArea: what it touches
Internal ChangesKind: in v2.1.251,
Internal ChangesSection of the release
What

Internal shell state now distinguishes a command pushed to the background so a message queued for the model could reach it from one backgrounded for other reasons, such as a plugin aborting the turn. The PowerShell command result carries this marker alongside the existing background fields. None of it surfaces in the interface while using Claude Code.

Details
  • a backgroundedToDeliverMessage field is set on the result of a backgrounded PowerShell command and passed through with the other background fields
  • the field is documented as true only when the command was moved to the background so a message queued for the model could reach it
  • commands backgrounded for any other cause leave the field unset, so the reason for backgrounding is no longer ambiguous internally
  • no flag, setting or environment variable exposes this, and there is no user-visible output change in this build
Evidence

backgroundedToDeliverMessage: b.backgroundedToDeliverMessage, True if the command was moved to the background so a message queued for the model could reach it

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

Feedback