{"version":"2.1.311","anchor":"cancelabort-result-carries-abort-reason-to-bridge","canonical_anchor":"cancelabort-result-carries-abort-reason-to-bridge","heading":"Linked apps now learn why a cancelled turn stopped","tier":"notice","area":"SDK","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311\/e\/cancelabort-result-carries-abort-reason-to-bridge","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311","markdown":"### Linked apps now learn why a cancelled turn stopped\n\nWhen you press Esc to cancel, Claude Code now tells linked apps who stopped the turn, whether another follows, and what was cut off\n\n**What**\n\nA turn is one round of Claude working on your request. When you press Esc to cancel a turn, Claude Code reports the result to any app linked to your session from elsewhere. That report used to carry no details. It now says:\n\n- Who stopped it: stop, send-now or other\n\n- Whether another turn will run straight after\n\n- A best guess at what was interrupted: tools that were running, or a reply still being written\n\n**Why**\n\nApps linked to your session can now tell why a turn ended instead of only seeing that it did.\n\n- Area: SDK\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}