{"version":"2.1.321","anchor":"bash-allow-rule-check-refactored","canonical_anchor":"bash-allow-rule-check-refactored","heading":"Check for exact-match Bash allow rules reworked","tier":"notice","area":"Permissions","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321\/e\/bash-allow-rule-check-refactored","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321","markdown":"### Check for exact-match Bash allow rules reworked\n\nClaude Code now decides whether an exact-match Bash allow rule applies using new logic, not a plain text comparison\n\n**Unclear.** Whether this changes which Bash commands prompt for permission is not known.\n\n**What**\n\nAllow rules let you approve specific Bash commands in advance so Claude Code does not ask each time. When deciding whether an exact-match allow rule covers a command, Claude Code now uses new logic. Before, it simply checked that the rule's text equalled the command with surrounding spaces trimmed.\n\n**Why**\n\nThis affects when Claude Code asks for permission to run Bash commands, so watch whether commands you have allowed still go through without a prompt.\n\n- Area: Permissions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: yes"}