{"version":"2.1.309","anchor":"permission-rule-physical-twin-lookup-simplified","canonical_anchor":"permission-rule-physical-twin-lookup-simplified","heading":"Symlinked paths in permission rules are resolved in a simpler way","tier":"internal","area":"Permissions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.309\/e\/permission-rule-physical-twin-lookup-simplified","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.309","markdown":"### Symlinked paths in permission rules are resolved in a simpler way\n\nFinding the real folder behind a permission rule's path no longer logs an error when it fails\n\n**Unclear.** Whether symlinked paths still match permission rules exactly as before is not known.\n\n**What**\n\nA permission rule can name a path that is really a symlink, a shortcut pointing to another location. When Claude Code works out the real location behind the start of such a path, it now uses a single step that gives no result if it fails. It no longer catches the failure and logs \"Could not resolve the physical twin of rule prefix\".\n\n**Why**\n\nThis affects how paths that go through symlinks are matched against your permission rules.\n\n- Area: Permissions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 0\/5\n- Scope: individual\n- Heads-up: no"}