{"version":"2.1.275","anchor":"path-checks-for-local-dirowner-repo-args-now-detect-network","canonical_anchor":"path-checks-for-local-dirowner-repo-args-now-detect-network","heading":"Path checks for local-dir\/owner-repo args now detect network-location symlinks","tier":"notice","area":"Permissions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.275\/e\/path-checks-for-local-dirowner-repo-args-now-detect-network","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.275","markdown":"### Path checks for local-dir\/owner-repo args now detect network-location symlinks\n\nDirectory and repo path arguments are now checked for symlinks that sneak in a network location\n\n**What**\n\nWhen Claude Code is given a path as a local-directory or owner\/repo argument and needs to check it (via `stat`), it now does more validation first:\n\n- It outright rejects Windows device-namespace paths (those starting with `\\\\?\\` or `\\\\.\\`), since these can't be safely checked for symlinks\n\n- For other paths, it walks the chain of symlinks (the ancestry of links) to see if the path passes through a symlink pointing to a network location, or to a link target that can't be read\n\nIf either case is found, it refuses the path with a specific error instead of proceeding.\n\n**Why**\n\nA symlink pointing to a network location could let a path argument silently redirect Claude Code to read from or interact with a remote location instead of the local one you intended. Rejecting these cases up front avoids that kind of surprise redirection.\n\n- Area: Permissions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}