What probably matters to youSection of the release
What
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.
Details
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 cancelled array, with still_queued always 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