{"version":"2.1.317","anchor":"auto-allow-rules-excluded-from-content-rule-matching","canonical_anchor":"auto-allow-rules-excluded-from-content-rule-matching","heading":"Some allow rules are now left out when Claude Code matches permission rules","tier":"notice","area":"Permissions","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317\/e\/auto-allow-rules-excluded-from-content-rule-matching","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317","markdown":"### Some allow rules are now left out when Claude Code matches permission rules\n\nWhen looking up which permission rules match a tool call, Claude Code now skips certain allow rules it previously included\n\n**Unclear.** Which allow rules are now skipped is not stated.\n\n**What**\n\nPermission rules are the settings that decide whether a tool may run without asking you. When Claude Code looks up which rules apply to a tool call, it used to return every rule matching the tool name, the content and the behaviour. It now skips some allow rules, based on a check of the rule's text.\n\n**Why**\n\nThis can change which of your allow rules take effect for a given tool call.\n\n- Area: Permissions\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: yes"}