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.219 Home All releases ←olderv2.1.218 v2.1.220newer→
Claude Code v2.1.219

interrupt control request can now cancel the whole queue (cancel_queued)

Use it now
Useful4 Signal0
SDK Protocol Notable not in their notes

An interrupt can now clear your whole queued command backlog at once and report what it cancelled.

cancel_queuedinterrupt_cancel_queued_v1
What

The control-protocol interrupt request accepts an optional cancel_queued boolean that clears queued main-thread commands along with the in-flight turn, and reports which uuids it killed.

Details
  • When cancel_queued === !0, every uuid-stamped main-thread command still queued, including ones dequeued for the imminent turn but not yet reachable by the abort, gets a terminal cancelled lifecycle event.
  • The response comes back with still_queued: [] and the cancelled uuids on a new optional cancelled field.
  • Without the flag, the previous still_queued behaviour is unchanged.
  • The capability string interrupt_cancel_queued_v1 is advertised on system/init next to interrupt_receipt_v1 and msg_lifecycle_v1, so clients can feature-detect it. None of these strings exist in v2.1.218.
  • The in-process SDK client's interrupt() wrapper does not send the flag, so this is for control-protocol consumers only.
Evidence

interrupt_cancel_queued_v1

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