{"version":"2.1.290","anchor":"permission-rule-wildcard-matching-reworked","canonical_anchor":"permission-rule-wildcard-matching-reworked","heading":"Wildcards in permission rules are matched differently","tier":"notice","area":"Permissions","scope":"both","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290\/e\/permission-rule-wildcard-matching-reworked","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290","markdown":"### Wildcards in permission rules are matched differently\n\nPermission rules with wildcards are now checked against a tool's name and its other names, replacing the old ** handling\n\n**Unclear.** Exactly which rules now match differently than before is not clear.\n\n**What**\n\nPermission rules decide which tools Claude Code may use without asking you. A rule containing a wildcard, a * that stands for any text, is now checked against the tool's name and also its other names. Before, Claude Code turned runs of ** into a single * and applied a length check.\n\n**Why**\n\nThis may change which tools a wildcard rule applies to.\n\n- Area: Permissions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: both\n- Heads-up: yes"}