{"version":"2.1.305","anchor":"allow-rule-with-mid-pattern-gets-a-security-notice","canonical_anchor":"allow-rule-with-mid-pattern-gets-a-security-notice","heading":"Allow rules with :* in the middle now get a security warning","tier":"notice","area":"Permissions","scope":"both","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.305\/e\/allow-rule-with-mid-pattern-gets-a-security-notice","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.305","markdown":"### Allow rules with `:*` in the middle now get a security warning\n\nAn allow rule with :* anywhere but the end now gets a security warning saying :* is read as a wildcard\n\n**What**\n\nAllow rules are permission rules that let Claude Code run matching actions without asking. In a rule, `:*` matches anything. When `:*` sits somewhere other than the end of an allow rule, Claude Code now adds a security notice saying the rule reads its `:*` as a wildcard and advising an exact value instead. Before, such rules got only a plain warning. A new notification area shows security warnings.\n\n**Why**\n\nA rule with `:*` in the middle can allow much more than intended, and you now get a visible warning about it.\n\n- Area: Permissions\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5\n- Scope: both\n- Heads-up: no"}