{"version":"2.1.318","anchor":"auto-allow-rule-matching-for-a-command-now-falls-through-to","canonical_anchor":"auto-allow-rule-matching-for-a-command-now-falls-through-to","heading":"Commands that exactly match an allow rule now get one more check","tier":"notice","area":"Permissions","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318\/e\/auto-allow-rule-matching-for-a-command-now-falls-through-to","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318","markdown":"### Commands that exactly match an allow rule now get one more check\n\nWhen a command exactly matches one of your allow rules, Claude Code now runs a further check before deciding instead of returning the earlier decision\n\n**Unclear.** It is not clear what the extra check tests or in which cases it changes the outcome for a matching allow rule.\n\n**What**\n\nAn allow rule tells Claude Code it may run a given command without asking you first. When a command exactly matches the text of such a rule, Claude Code now runs an additional check before it settles the decision. Previously an exact match simply returned the earlier decision.\n\n**Why**\n\nThis can change the permission decision for commands that match a rule exactly, so a command you expected to run without asking might be handled differently.\n\n- Area: Permissions\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: yes"}