{"version":"2.1.301","anchor":"permission-rules-usersettings-absolute-path-handling","canonical_anchor":"permission-rules-usersettings-absolute-path-handling","heading":"Absolute-path permission rules in user settings are handled differently","tier":"notice","area":"Permissions","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.301\/e\/permission-rules-usersettings-absolute-path-handling","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.301","markdown":"### Absolute-path permission rules in user settings are handled differently\n\nPermission rules in user settings that start with `\/` are no longer resolved against a root folder in the permission check\n\n**Unclear.** It is not clear under which condition this applies, so whether your absolute-path rules match differently is unknown.\n\n**What**\n\nPermission rules decide what Claude Code may do without asking. Rules in your user settings that begin with `\/`, an absolute path, are no longer resolved against a root folder when Claude Code checks permissions, and user settings are left out of the list of rule roots. Before, every settings scope was included.\n\n**Why**\n\nThis changes how those rules are matched against files.\n\n- Area: Permissions\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: yes"}