{"version":"2.1.288","anchor":"permission-matcher-for-bash-patterns-tracks-judgespatterns","canonical_anchor":"permission-matcher-for-bash-patterns-tracks-judgespatterns","heading":"Permission rules for shell commands change how patterns are matched","tier":"internal","area":"Permissions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288\/e\/permission-matcher-for-bash-patterns-tracks-judgespatterns","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288","markdown":"### Permission rules for shell commands change how patterns are matched\n\nClaude Code's matching of permission rules against shell command patterns changes and may affect commands joined together\n\n**Unclear.** It is not clear which permission checks use the new matching or whether any rule now matches differently.\n\n**What**\n\nPermission rules decide which shell commands Claude may run without asking. The code that matches these rules against command patterns takes an extra input. When asked, it now reports whether it judged the patterns; otherwise it requires a pattern matcher to be present. Previously it simply returned yes in that case.\n\n**Why**\n\nThis may change which rules match in unusual cases, such as compound commands (several commands joined together, for example with `&&`).\n\n- Area: Permissions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}