{"version":"2.1.281","anchor":"protected-home-folder-list-extended-with-windows-legacy-fold","canonical_anchor":"protected-home-folder-list-extended-with-windows-legacy-fold","heading":"Protected home-folder list extended with Windows legacy folders and OneDrive, with WSL-aware matching","tier":null,"area":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/protected-home-folder-list-extended-with-windows-legacy-fold","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Protected home-folder list extended with Windows legacy folders and OneDrive, with WSL-aware matching\n\nMore Windows home folders, including legacy folders and OneDrive PowerShell folders, are now treated as dangerous, with WSL-aware matching\n\n**What**\n\nClaude Code keeps a list of folders inside your home folder that it treats as dangerous. That list now also includes:\n\n- `Application Data`\n\n- `Local Settings`\n\n- `Cookies`\n\n- `NetHood`\n\n- `PrintHood`\n\n- `Recent`\n\n- `SendTo`\n\n- `My Documents\/PowerShell`\n\n- `OneDrive*\/Documents\/PowerShell` and `OneDrive*\/Documents\/WindowsPowerShell`\n\n`OneDrive*` matches any folder whose name starts with OneDrive, such as \"OneDrive - Org\".\n\nMatching also works under WSL (Windows Subsystem for Linux, which runs Linux on a Windows machine), where Windows drives appear as `\/mnt\/<drive>` paths. On Windows, folders that contain these folders are now caught too.\n\n**Why**\n\nThese folders hold Windows system data and PowerShell startup files. Covering them, including work OneDrive folders and the same folders seen from WSL, makes it harder for them to be touched without extra scrutiny."}