{"version":"2.1.282","anchor":"warnings-for-permission-rules-that-mix-with-the-prefix","canonical_anchor":"warnings-for-permission-rules-that-mix-with-the-prefix","heading":"Warnings for permission rules that mix with :","tier":"notice","area":"Permissions","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.282\/e\/warnings-for-permission-rules-that-mix-with-the-prefix","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.282","markdown":"### Warnings for permission rules that mix `*` with `:*`\n\nPermission rules that combine `*` with the `:*` prefix form, or put `:*` mid-rule, now come with a warning explaining how they match\n\n**What**\n\nPermission rules tell Claude Code which actions it may take without asking, such as running certain shell commands. Claude Code now warns about two kinds of rule that do not match the way they look, while still accepting them:\n\n- A rule that mixes `*` with a trailing `:*` is matched as a plain prefix, and the `*` is taken literally rather than as a wildcard.\n\n- A rule with `:*` anywhere but the end is matched as a `*` wildcard with a literal colon, not as the trailing `:*` prefix form.\n\nThe advice in the warning is different for allow rules and for other rules.\n\n**Why**\n\nA rule like `Bash(git *:*)` never matched anything and gave no sign of it. Now you are told, so you can fix the rule.\n\n- Area: Permissions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}