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.242 Home All releases ←olderv2.1.241 v2.1.243newer→
Claude Code v2.1.242

Cloud sessions report queued commands dropped by an interrupt

Use it now
Useful3 Signal3
Cloud Sessions not in their notes

Headless cloud clients now see a cancelled status for each queued command an interrupt dropped.

--cloud
What

A tool driving a cloud session through the headless --cloud client now gets a 'cancelled' status, and only that status, for each queued command an interrupt with cancel_queued:true dropped, so it can tell that those commands will never run.

Details
  • The cancellation messages follow the interrupt's own success response and are not ordered against the result of the turn that was interrupted.
  • Identifiers you do not recognise may appear, because another client connected to the same session may have queued the prompt.
  • Documented for the stdout stream in -p and SDK sessions, headless --cloud client only.
Evidence

A host driving a cloud-hosted session through the headless --cloud client also receives 'cancelled' (and only that state) after its interrupt with cancel_queued:true

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