You'll noticeTier: how much it should matter to you
1Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
PermissionsArea: what it touches
ImprovementsKind: in v2.1.282,
ImprovementsSection of the release
What
Before Claude Code decides whether it may touch a file, it works out the file's full, real location on disk. Some locations it deliberately does not try to resolve this way, because they point somewhere other than an ordinary local folder. Network paths, which point to files on another machine, were already among them.
macOS has a few special kinds of path that reach files by a different route than an ordinary folder name. Claude Code now puts paths that use any of these in that same group and skips resolving them, just as it does for network paths:
/.vol
/.file
/.nofollow
/.resolve
Why
These macOS paths can lead to the same file as an ordinary path while looking nothing like it. Claude Code no longer treats them as ordinary local paths when it works out where a file really lives, which matters for checks that decide what Claude Code is allowed to read or change based on where a file is.
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 doubtIt is not confirmed that this was done to close a way around Claude Code's permission or sandbox checks, or which checks depend on it.
Anthropic's release notes agreeFixed CLAUDE.md and rules being read at startup through a repository symlink reaching macOS's /Network via .. or a /.vol-style kernel path…
