{"version":"2.1.265","anchor":"bash-permission-matching-now-accounts-for-a-leading-cd","canonical_anchor":"bash-permission-matching-now-accounts-for-a-leading-cd","heading":"Bash permission matching now accounts for a leading \"cd <cwd> &&\" wrapper","tier":"notice","area":"Permissions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265\/e\/bash-permission-matching-now-accounts-for-a-leading-cd","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265","markdown":"### Bash permission matching now accounts for a leading \"cd <cwd> &&\" wrapper\n\nBash permission rules now match commands even when prefixed with \"cd &&\"\n\n**What**\n\nWhen Claude Code checks whether a Bash command is allowed by your permission rules, it now also recognizes commands written as `cd <folder> && <command>` as matching a rule written for the bare `<command>`, as long as the folder matches the current working directory.\n\n**Why**\n\nBefore this, a permission rule written for a plain command could fail to match if Claude first changed directory and chained the command with `&&`, even though the actual working directory was the same one the rule expected. This closes that gap so such commands are recognized correctly.\n\n- Area: Permissions\n- Names: `cd`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}