{"version":"2.1.311","anchor":"bash-tool-refuses-to-start-a-duplicate-of-a-command-already","canonical_anchor":"bash-tool-refuses-to-start-a-duplicate-of-a-command-already","heading":"Bash tool refuses to start a command already running in the background","tier":"notice","area":"Bash","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311\/e\/bash-tool-refuses-to-start-a-duplicate-of-a-command-already","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311","markdown":"### Bash tool refuses to start a command already running in the background\n\nIf the same command in the same folder is already running in the background, the Bash tool now refuses to start it again and says where it is\n\n**Unclear.** What the further check is, and so whether the refusal applies in a given session, is not clear.\n\n**What**\n\nThe Bash tool runs shell commands for Claude. Before running one, it now checks whether the same command, in the same folder, was already moved to the background and is still running. If so, it does not start it and replies with a message beginning \"Not started: this same command, in this directory, was moved to the background and has been running for\", which gives the task ID and the file its output is written to.\n\nThis refusal only applies when the tool for stopping background tasks is available and a further check passes.\n\nThe Bash tool's own description also changed in this release: it now says a `cd` carries over to the next call only in the main session, when the command succeeds and ends inside the working directories.\n\n**Why**\n\nThis stops Claude from launching a second copy of a long-running command by mistake. Instead it is pointed at the copy already running.\n\n- Area: Bash\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: yes"}