Send interrupt with cancel_queued true to stop the current turn and everything queued behind it.
What's wrong with this entry?
The interrupt control_request takes a new optional boolean cancel_queued that sweeps the whole main-thread queue along with the abort, so a remote UI can offer a "Stop means stop everything" button without walking uuids one at a time.
- When true, every uuid-stamped main-thread command still queued, and any already dequeued for the imminent turn, is cancelled alongside the abort and emits a terminal 'cancelled' lifecycle
- The response returns those uuids under a new
cancelledarray, withstill_queuedalways empty - A wrapper that wants per-uuid control leaves the flag false and keeps using cancel_async_message
- Absent or false preserves the existing interrupt_receipt_v1 behaviour exactly
{"type":"control_request","request":{"subtype":"interrupt","cancel_queued":true}}When true, the interrupt also cancels every uuid-stamped main-thread command still in the queue
Strings lifted out of the shipped bundle, so the claim above can be checked against them.