{"version":"2.1.304","anchor":"globpermission-patterns-get-a-cost-cap-and-a-directory-subt","canonical_anchor":"globpermission-patterns-get-a-cost-cap-and-a-directory-subt","heading":"Permission path patterns get a length limit and can match whole folders","tier":"notice","area":"Permissions","scope":"both","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304\/e\/globpermission-patterns-get-a-cost-cap-and-a-directory-subt","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304","markdown":"### Permission path patterns get a length limit and can match whole folders\n\nOver-long path patterns in permission rules are now flagged as too costly, and a pattern can also match everything inside the folder it names\n\n**Unclear.** The length limit is not stated, nor whether a pattern that is too long ends up as a refusal or an error.\n\n**What**\n\nPermission rules can name files or folders with wildcard patterns. Claude Code has changed how it turns those patterns into matches:\n\n- A pattern that is too long is now marked as too costly to check instead of being matched without any limit.\n\n- A second match is built for each pattern so it also covers paths underneath the one it names, the way a folder covers what is inside it.\n\n- Paths in permission patterns are now resolved in a way specific to patterns.\n\n**Why**\n\nThe limit protects Claude Code from patterns that would take a very long time to check. The folder matching may change which paths an existing rule covers, so it is worth checking that rules still allow and block what you expect.\n\n- Area: Permissions\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5\n- Scope: both\n- Heads-up: yes"}