{"version":"2.1.285","anchor":"bash-abort-before-spawn-check-and-background-timeout","canonical_anchor":"bash-abort-before-spawn-check-and-background-timeout","heading":"Bash commands cancelled just before starting are now cleaned up","tier":"notice","area":"Bash Tool","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285\/e\/bash-abort-before-spawn-check-and-background-timeout","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285","markdown":"### Bash commands cancelled just before starting are now cleaned up\n\nA shell command cancelled right before it starts is now cleaned up, and the Bash tool now states time limits for background commands\n\n**What**\n\nWhen a shell command is cancelled just before it starts, Claude Code now cleans up after it.\n\nIn this release's description of the Bash tool, which is what Claude reads to learn how to run commands, the 10-minute limit is said to apply to foreground commands. The description also gives a limit for background commands: 1800000 ms (30 minutes) by default and at most 7200000 ms (2 hours).\n\n**Why**\n\nCancelling a command while it is starting no longer leaves stray output files behind.\n\n- Area: Bash Tool\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}