Under the hoodTier: how much it should matter to you
1Useful: my rating, 1 to 5
0Signal: worth watching, 1 to 5
PermissionsArea: what it touches
Internal ChangesKind: in v2.1.309,
Internal ChangesSection of the release
Unclear Whether symlinked paths still match permission rules exactly as before is not known.
What
A 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".
Why
This affects how paths that go through symlinks are matched against your permission rules.
How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtWhether symlinked paths still match permission rules exactly as before is not known.