{"version":"2.1.318","anchor":"permission-rule-matching-now-consumes-a-second-list-of-rules","canonical_anchor":"permission-rule-matching-now-consumes-a-second-list-of-rules","heading":"Permission rule matching now checks a second list of rules","tier":"internal","area":"Permissions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318\/e\/permission-rule-matching-now-consumes-a-second-list-of-rules","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318","markdown":"### Permission rule matching now checks a second list of rules\n\nWhen matching permission rules, Claude Code now also checks a second list of rules after the first\n\n**Unclear.** It is not clear which rules the second list holds, so the effect on your permissions is unknown.\n\n**What**\n\nPermission rules decide which actions Claude Code may take without asking you. When matching them, Claude Code used to go through only one list of rules. It now goes through a second list afterwards and keeps each matching rule that still has uses left.\n\n**Why**\n\nThis could change which of your permission rules are matched, or how duplicates are handled.\n\n- Area: Permissions\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 4\/5\n- Scope: individual\n- Heads-up: no"}