{"version":"2.1.300","anchor":"interrupted-bash-tasks-interrupt-no-longer-ignored-in-some","canonical_anchor":"interrupted-bash-tasks-interrupt-no-longer-ignored-in-some","heading":"Interrupting can now stop a running shell command in some cases","tier":"notice","area":"Bash Tool","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300\/e\/interrupted-bash-tasks-interrupt-no-longer-ignored-in-some","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300","markdown":"### Interrupting can now stop a running shell command in some cases\n\nInterrupting Claude Code can now stop a running shell command in some cases, where before an interrupt always left the command running\n\n**Unclear.** Which commands are now stopped by an interrupt, for example foreground or background ones, is not shown.\n\n**What**\n\nWhen Claude runs a shell command (a command typed into a terminal) and you interrupt, the command used to keep running every time. Now a check decides: in some cases the interrupt stops the command's process.\n\n**Why**\n\nPressing Esc may now end a running command where it used to be left alone.\n\n- Area: Bash Tool\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: yes"}