{"version":"2.1.285","anchor":"bash-tool-call-cancellation-now-reports-rannothing","canonical_anchor":"bash-tool-call-cancellation-now-reports-rannothing","heading":"Claude is told plainly when a stopped shell command never ran","tier":"notice","area":"Bash Tool","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285\/e\/bash-tool-call-cancellation-now-reports-rannothing","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285","markdown":"### Claude is told plainly when a stopped shell command never ran\n\nWhen a shell command is cancelled before running, Claude now gets a clear signal that nothing ran, with a message based on who stopped it\n\n**Unclear.** The new wording of the cancellation message is not known.\n\n**What**\n\nThe Bash tool is how Claude runs shell commands. When a Bash command is cancelled in the two cases handled here, the result Claude receives now states outright that nothing ran. The accompanying message is built in one shared way based on who stopped the call, replacing the separate wording each case used, such as a note that the call reached its deadline.\n\nSeparately, the Bash tool's own description, as captured under this release, now says the 10-minute maximum timeout applies to a foreground command.\n\n**Why**\n\nClaude gets a consistent signal that a cancelled command never started, so it is less likely to assume it had an effect.\n\n- Area: Bash Tool\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}