{"version":"2.1.307","anchor":"bash-path-safety-check-now-surfaces-only-safety-check-asks-w","canonical_anchor":"bash-path-safety-check-now-surfaces-only-safety-check-asks-w","heading":"Bash permission prompts now report the safety-check path first","tier":"notice","area":"Permissions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.307\/e\/bash-path-safety-check-now-surfaces-only-safety-check-asks-w","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.307","markdown":"### Bash permission prompts now report the safety-check path first\n\nWhen several file paths in a Bash command fail checks, Claude Code now reports the first safety-check problem instead of the first disallowed path\n\n**What**\n\nBefore running a shell command through the Bash tool, Claude Code checks the file paths the command touches. When more than one path fails, it used to report the first path that was not allowed. It now reports only the first path that failed a safety check, which is a check that makes Claude Code stop and ask you before doing something risky. Two cases still behave the old way:\n\n- a rule you set denies one of the paths\n\n- the command is `cp` and its last path is a different one\n\n**Why**\n\nFor commands that touch several paths, the permission prompt you see may point at a different path than it did before.\n\n- Area: Permissions\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}