{"version":"2.1.307","anchor":"headless-interrupt-can-requeue-the-taken-message","canonical_anchor":"headless-interrupt-can-requeue-the-taken-message","heading":"Interrupting headless Claude Code puts the current message back in the queue","tier":"notice","area":"Agents","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.307\/e\/headless-interrupt-can-requeue-the-taken-message","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.307","markdown":"### Interrupting headless Claude Code puts the current message back in the queue\n\nIn headless and SDK use, an interrupt without `cancelQueued` now puts the message being handled back in the queue instead of dropping it\n\n**What**\n\nHeadless mode means running Claude Code with no interactive screen, for example from a script or through the Agent SDK. When you interrupt in this mode, Claude Code now deals with the message it was working on in one of two ways:\n\n- With `cancelQueued` set, that message is finished off along with the cancelled queue.\n\n- Without `cancelQueued`, the message goes back into the queue, is marked as already sent, and a \"queued\" event is reported for it.\n\nAn interrupt no longer drops the message that was being handled.\n\n**Why**\n\nPrompts sent through the SDK or a script are no longer lost when you interrupt. If you do not want them to come back, pass `cancelQueued`.\n\n- Area: Agents\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}