{"version":"2.1.282","anchor":"path-canonicalisation-treats-macos-vol-file-nofollow","canonical_anchor":"path-canonicalisation-treats-macos-vol-file-nofollow","heading":"macOS special paths like \/.vol are now handled the same way as network paths","tier":"notice","area":"Permissions","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.282\/e\/path-canonicalisation-treats-macos-vol-file-nofollow","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.282","markdown":"### macOS special paths like \/.vol are now handled the same way as network paths\n\nWhen working out a file's real location, Claude Code now treats macOS special paths such as \/.vol and \/.nofollow the same way it treats network paths\n\n**Unclear.** It 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.\n\n**What**\n\nBefore 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.\n\nmacOS 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:\n\n- `\/.vol`\n\n- `\/.file`\n\n- `\/.nofollow`\n\n- `\/.resolve`\n\n**Why**\n\nThese 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.\n\n- Area: Permissions\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}