{"version":"2.1.311","anchor":"bash-call-refused-if-working-directory-changed-since-permiss","canonical_anchor":"bash-call-refused-if-working-directory-changed-since-permiss","heading":"Shell commands are refused if their folder changed after approval","tier":"notice","area":"Bash Safety","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311\/e\/bash-call-refused-if-working-directory-changed-since-permiss","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311","markdown":"### Shell commands are refused if their folder changed after approval\n\nA Bash command is not run if its working directory changed between the permission check and running it; you are asked to retry\n\n**What**\n\nBefore Claude Code runs a shell command, it checks whether the command is allowed, including which folder it runs in. If that folder no longer leads to the same place by the time the command would run, the command is now refused. That can happen because the folder was deleted, because part of its path was replaced, or because it cannot be examined. The message says the call was not run and asks for it to be made again, so it gets checked afresh.\n\n**Why**\n\nThis closes a gap between approving a command and running it. A command cleared for one folder can no longer end up running in a different one because the folder was swapped in between.\n\n- Area: Bash Safety\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: yes"}