{"version":"2.1.319","anchor":"bash-permission-rule-matching-wildcard-rules-checked-agains","canonical_anchor":"bash-permission-rule-matching-wildcard-rules-checked-agains","heading":"Wildcard Bash allow rules no longer approve compound or unusual commands","tier":"notice","area":"Permissions","scope":"both","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319\/e\/bash-permission-rule-matching-wildcard-rules-checked-agains","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319","markdown":"### Wildcard Bash allow rules no longer approve compound or unusual commands\n\nWildcard Bash permission rules now get an extra check, so a compound or unusual command no longer matches them\n\n**Unclear.** Which wildcard rules get the extra check is not stated.\n\n**What**\n\nPermission rules decide which commands Claude Code may run without asking you. A wildcard rule uses `*` to match many commands at once. Before, a command that fit the wildcard pattern matched the rule straight away.\n\nNow Claude Code also splits the command into its separate words in two ways and compares the results. If they disagree, for example because of unusual quoting or because the command chains several commands together, the wildcard rule does not match. The extra check applies only to certain rules, and only to commands under a length limit.\n\n**Why**\n\nA wildcard allow rule can now approve fewer commands automatically, so a command dressed up to look like an allowed one gets to the usual permission check instead.\n\n- Area: Permissions\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5\n- Scope: both\n- Heads-up: yes"}