{"version":"2.1.323","anchor":"bash-permission-rule-matching-wildcard-allow-rules-stricter","canonical_anchor":"bash-permission-rule-matching-wildcard-allow-rules-stricter","heading":"Bash allow rules with wildcards are checked more strictly","tier":"notice","area":"Permissions","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/bash-permission-rule-matching-wildcard-allow-rules-stricter","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### Bash allow rules with wildcards are checked more strictly\n\nWildcard allow rules for Bash commands now go through an extra rejection check, and each command is matched in a second parsed form\n\n**Unclear.** Which commands the extra check rejects, and so which allow rules now stop matching, is not stated.\n\n**What**\n\nPermission rules decide which shell commands Claude can run without asking you. Claude Code changed how a Bash command is matched against these rules:\n\n- Wildcard rules that are not deny or ask rules now have an extra check that can reject a command even when the pattern seems to fit.\n\n- Claude Code now reads each command in a second way and also matches that version against your rules when it differs from the first.\n\n**Why**\n\nThis changes which Bash commands are approved automatically by your rules. A command your wildcard allow rule used to cover may now trigger a permission prompt.\n\n- Area: Permissions\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: yes"}