{"version":"2.1.321","anchor":"interrupt-cancel-semantics-and-cloud-cloud-docs-updated","canonical_anchor":"interrupt-cancel-semantics-and-cloud-cloud-docs-updated","heading":"A plain interrupt can now cancel resent messages in remote sessions","tier":"notice","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321\/e\/interrupt-cancel-semantics-and-cloud-cloud-docs-updated","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321","markdown":"### A plain interrupt can now cancel resent messages in remote sessions\n\nIn remote sessions, behind a flag, a plain interrupt can cancel messages the server resent; `--cloud` now reports what was cancelled\n\n**What**\n\nAn interrupt is the signal that stops Claude Code mid-task. Before, only an interrupt sent with the option to cancel queued commands removed those commands.\n\nThe documented behaviour for programs that control Claude Code has changed in two places:\n\n- Remote sessions: behind a flag, a plain interrupt can now also cancel messages the server had sent again.\n\n- `--cloud`: the list of cancelled messages is now built from the cancelled list in the server's receipt.\n\n**Why**\n\nTools built on the SDK, the toolkit for controlling Claude Code from your own programs, and remote clients that send a message again after it shows as cancelled should check this. A plain interrupt may now cancel more than it used to.\n\n- Area: Sessions\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}