{"version":"2.1.305","anchor":"permission-wildcard-warning-gains-a-short-securitynotice","canonical_anchor":"permission-wildcard-warning-gains-a-short-securitynotice","heading":"Wildcard permission warning gets a short one-line version","tier":"notice","area":"Permissions","scope":"both","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.305\/e\/permission-wildcard-warning-gains-a-short-securitynotice","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.305","markdown":"### Wildcard permission warning gets a short one-line version\n\nThe warning about a `*` placed before the rest of a command in a permission rule now also comes as a short one-line notice\n\n**What**\n\nPermission rules decide which commands Claude Code may run without asking. A rule can use `*` as a wildcard that matches anything. When a wildcard comes before the rest of the command, Claude Code warns you. That warning now also comes with a short one-line notice: \"allows any option at its * \u00b7 use an exact value\". The long warning is still there.\n\n**Why**\n\nThe short version is compact enough to show in the permission screens.\n\n- Area: Permissions\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: both\n- Heads-up: no"}