Claude Code v2.1.317 ·
Interrupts with no send-now answer now report "interrupted"
When an interrupt request gets no send-now value back, the result now reads "interrupted" instead of "stopped"
Under the hoodTier: how much it should matter to you
1Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
SDKArea: what it touches
Internal ChangesKind: in v2.1.317,
Internal ChangesSection of the release
What
When you interrupt Claude and the request comes back without a send-now value, the result is now "interrupted". It used to be "stopped".
Why
Anything that watches for this result in thin-client setups, where a lightweight client drives a session running elsewhere, sees a different word.
See this entry in the whole of v2.1.317 →
