You'll noticeTier: how much it should matter to you
3Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
SessionsArea: what it touches
Bug FixesKind: in v2.1.290,
Bug FixesSection of the release
Unclear It is not clear what decides which queued commands a cancel is aimed at, or whether this behaviour is switched on for everyone.
What
In 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.
Why
This 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.
How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtIt is not clear what decides which queued commands a cancel is aimed at, or whether this behaviour is switched on for everyone.