{"version":"2.1.265","anchor":"bash-command-comparison-for-approval-matching-reworked","canonical_anchor":"bash-command-comparison-for-approval-matching-reworked","heading":"Bash command comparison for approval matching reworked","tier":"notice","area":"Permissions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265\/e\/bash-command-comparison-for-approval-matching-reworked","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265","markdown":"### Bash command comparison for approval matching reworked\n\nThe check that matches bash commands for permission approval was rewritten to handle more command-prefix forms\n\n**What**\n\nWhen Claude Code decides whether two bash commands should be treated as the same for permission or approval purposes, it previously did this by stripping a literal `cd <directory> && ` prefix. That logic has been replaced with a more general comparison that also correctly handles the way Windows quotes a `cd` prefix.\n\n**Why**\n\nThis makes permission matching for bash commands more reliable on Windows, reducing cases where a command that should be recognized as already-approved is instead treated as new and prompts for approval again.\n\n- Area: Permissions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}