{"version":"2.1.318","anchor":"interrupt-receipt-and-cli-queued-at-interrupt-gain-held-mess","canonical_anchor":"interrupt-receipt-and-cli-queued-at-interrupt-gain-held-mess","heading":"Interrupting now also covers messages Claude Code has received but not yet queued","tier":"notice","area":"SDK","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318\/e\/interrupt-receipt-and-cli-queued-at-interrupt-gain-held-mess","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318","markdown":"### Interrupting now also covers messages Claude Code has received but not yet queued\n\nWhen you interrupt, the list of still-waiting messages now includes ones held back behind a model change or start-up work\n\n**What**\n\nWhen you interrupt Claude, Claude Code reports which of your messages are still waiting in `still_queued`. That list now also includes messages Claude Code has already read in but not yet put in the queue, for example because they were held back behind a model change or work done at start-up. It also covers a mark showing that a cancel is pending.\n\nThe diagnostic log line written at interrupt time also records more about the state of the current turn, such as whether a turn was still being wrapped up and how long it has been since the last result.\n\n**Why**\n\nPressing Stop now accounts for messages that were in transit, not only ones already queued, so they are not missed when you interrupt.\n\n- Area: SDK\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}