{"version":"2.1.281","anchor":"windows-documents-and-powershell-profile-folders-resolved-f","canonical_anchor":"windows-documents-and-powershell-profile-folders-resolved-f","heading":"Windows: Documents and PowerShell profile folders resolved for the remote-tools safety check","tier":null,"area":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/windows-documents-and-powershell-profile-folders-resolved-f","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Windows: Documents and PowerShell profile folders resolved for the remote-tools safety check\n\nOn Windows, Claude Code now locates your Documents and PowerShell profile folders for the check that offers local tools to cloud sessions\n\n**Unclear.** The finding does not say what happens when an overlap is actually found.\n\n**What**\n\nOn Windows, Claude Code can offer this machine's tools to cloud sessions. Before it does, a safety check makes sure the workspace does not overlap certain folders. New Windows-only code now finds your Documents folder in these ways:\n\n- It reads the `User Shell Folders` `Personal` value from the Windows registry.\n\n- It falls back to asking PowerShell for `$PROFILE`.\n\n- It also checks OneDrive Documents folders.\n\n- It turns mapped network drive letters into full network paths using `HKCU\\Network\\<drive>`.\n\nThe PowerShell and WindowsPowerShell profile folders found this way are included in the overlap check. The check also rejects network paths, paths on this computer's own host name, WSL host paths and short-form paths.\n\n**Why**\n\nIf this lookup fails, this machine's tools are not offered to cloud sessions until Claude Code next starts. If your tools are missing from a cloud session on Windows, restarting is the way to retry."}