{"version":"2.1.281","anchor":"auto-allow-path-check-no-longer-excludes-network-and-net-p","canonical_anchor":"auto-allow-path-check-no-longer-excludes-network-and-net-p","heading":"Auto-allow path check no longer excludes \/Network and \/net paths up front","tier":null,"area":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/auto-allow-path-check-no-longer-excludes-network-and-net-p","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Auto-allow path check no longer excludes \/Network and \/net paths up front\n\nA path check that lets some file access go ahead automatically no longer excludes \/Network and \/net paths first\n\n**Unclear.** The finding does not show whether `\/Network` and `\/net` paths are still blocked elsewhere, so the practical effect on what is allowed automatically is unclear.\n\n**What**\n\nClaude Code has a check that decides whether a file path is safe enough to allow automatically. It used to rule out two kinds of paths before anything else: `\/Network` and `\/net`, locations where network drives are mounted automatically. Those two early exclusions have been removed from this check. The check for reading files still uses them.\n\n**Why**\n\nIn practice, `\/Network` and `\/net` paths are no longer turned away at the start of this particular check."}