{"version":"2.1.317","anchor":"interrupt-send-now-fallback-result-renamed-from-stopped-to-i","canonical_anchor":"interrupt-send-now-fallback-result-renamed-from-stopped-to-i","heading":"Interrupts with no send-now answer now report \"interrupted\"","tier":"internal","area":"SDK","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317\/e\/interrupt-send-now-fallback-result-renamed-from-stopped-to-i","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317","markdown":"### Interrupts with no send-now answer now report \"interrupted\"\n\nWhen an interrupt request gets no send-now value back, the result now reads \"interrupted\" instead of \"stopped\"\n\n**What**\n\nWhen you interrupt Claude and the request comes back without a send-now value, the result is now \"interrupted\". It used to be \"stopped\".\n\n**Why**\n\nAnything that watches for this result in thin-client setups, where a lightweight client drives a session running elsewhere, sees a different word.\n\n- Area: SDK\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}