{"version":"2.1.295","anchor":"permission-rule-matching-gains-pattern-and-alias-source-path","canonical_anchor":"permission-rule-matching-gains-pattern-and-alias-source-path","heading":"Permission rules split into pattern rules and content rules when matched","tier":"notice","area":"Permissions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295\/e\/permission-rule-matching-gains-pattern-and-alias-source-path","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295","markdown":"### Permission rules split into pattern rules and content rules when matched\n\nAllow and deny rules are now grouped into `patterns` and `withContent` lists, which may change which rules match aliased skills\n\n**Unclear.** It is not stated which rule syntax the new pattern entries correspond to or which existing rules would now match differently.\n\n**What**\n\nPermission rules are the allow and deny entries that decide whether Claude may use a tool or skill without asking you. The way these rules are grouped and matched has changed.\n\n- The helper that groups allow and deny rules by tool now returns two separate lists, `patterns` and `withContent`, instead of a single list called `others`. Pattern rules keep their rule names.\n\n- The matcher for skills and tools now checks each `patterns` entry using both the rule and its rule name.\n\n- It checks `withContent` rules only when `aliasSources().length > 0`, which means only when the skill or tool has alias sources, that is, other names it can be known by.\n\nBefore, the matcher simply tested every entry in `others`.\n\n**Why**\n\nThis may change which permission rules match, especially for skills that are reached through an alias. If a rule starts or stops applying unexpectedly, this change may be the reason.\n\n- Area: Permissions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}