{"version":"2.1.290","anchor":"interrupt-before-turn-latch-gets-a-targeted-aim-remote-ca","canonical_anchor":"interrupt-before-turn-latch-gets-a-targeted-aim-remote-ca","heading":"A remote cancel no longer throws away every queued prompt","tier":"notice","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290\/e\/interrupt-before-turn-latch-gets-a-targeted-aim-remote-ca","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290","markdown":"### A remote cancel no longer throws away every queued prompt\n\nA cancel sent from outside the terminal now targets specific queued input instead of discarding everything you had queued\n\n**Unclear.** It is not clear what decides which queued commands a cancel is aimed at, or whether this behaviour is switched on for everyone.\n\n**What**\n\nIn sessions driven from somewhere other than your terminal, such as a remote session or a program using the Agent SDK, you can queue a new prompt while a cancel request is also on its way. Before, a cancel that arrived before Claude's next turn started discarded all queued input. Now the cancel is aimed at particular queued commands, so input it was not aimed at stays in the queue. The cancel also reports whether a turn was actually running when it arrived.\n\n**Why**\n\nThis affects what happens when a remote interrupt and a fresh prompt arrive at nearly the same moment. A prompt you sent after cancelling should be less likely to vanish.\n\n- Area: Sessions\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}