{"version":"2.1.292","anchor":"path-safety-check-for-dangerous-write-targets-windowswslu","canonical_anchor":"path-safety-check-for-dangerous-write-targets-windowswslu","heading":"Dangerous write locations now include network shares, WSL and drive roots","tier":"notice","area":"Permissions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.292\/e\/path-safety-check-for-dangerous-write-targets-windowswslu","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.292","markdown":"### Dangerous write locations now include network shares, WSL and drive roots\n\nClaude Code's check for risky places to write now flags Windows network admin shares, device paths, WSL mounts, \/.vol on macOS and root folders\n\n**What**\n\nClaude Code checks whether a place it is about to write to is risky. That check now flags:\n\n- administrative shares on Windows network paths, addresses that begin with two slashes\n\n- device paths\n\n- mounts from WSL, the Windows Subsystem for Linux\n\n- `\/.vol` on macOS\n\n- the root of the file system\n\n- the working folder itself\n\n- the drive roots of the working folder\n\n**Why**\n\nIt guards against writes aimed at locations so broad that a mistake could damage a lot at once.\n\n- Area: Permissions\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}