{"version":"2.1.305","anchor":"permission-rule-path-check-used-the-wrong-variable-fixed","canonical_anchor":"permission-rule-path-check-used-the-wrong-variable-fixed","heading":"Permission rules are checked for file paths against the right values","tier":"notice","area":"Permissions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.305\/e\/permission-rule-path-check-used-the-wrong-variable-fixed","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.305","markdown":"### Permission rules are checked for file paths against the right values\n\nThe check for whether a permission rule is a file path rule now looks at that rule's own text and where it came from\n\n**Unclear.** Which permission rules now behave differently is not known.\n\n**What**\n\nPermission rules decide what Claude Code may do without asking you. One check decides whether a rule refers to a file path, meaning it starts with `~\/` or with a single `\/`. That check now looks at the rule's own text and the place the rule came from. Before, it looked at other values.\n\n**Why**\n\nThis appears to fix which rules are treated as path rules.\n\n- Area: Permissions\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}