{"version":"2.1.302","anchor":"aborted-tool-calls-can-be-abandoned-after-a-grace-period","canonical_anchor":"aborted-tool-calls-can-be-abandoned-after-a-grace-period","heading":"A tool that ignores an interrupt can be given up on after a grace period","tier":"notice","area":"Elsewhere","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.302\/e\/aborted-tool-calls-can-be-abandoned-after-a-grace-period","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.302","markdown":"### A tool that ignores an interrupt can be given up on after a grace period\n\nWhen you interrupt Claude and a running tool does not stop, Claude Code can now mark it interrupted after a grace period\n\n**Unclear.** The default length of the grace period, and so whether this timer runs by default, is not settled.\n\n**What**\n\nA tool call is a single action Claude takes, such as running a command or reading a file. When you interrupt Claude, running tools are told to stop.\n\nIf a tool does not stop, Claude Code can now wait a grace period and then treat the call as finished, recording it as interrupted by the user. If the grace period is set to zero, no timer runs and this does not happen.\n\n**Why**\n\nA tool that hangs should no longer stop an interrupt from taking effect.\n\n- Area: Elsewhere\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}