The install notes assume File Explorer + install.cmd. Two known rough edges from prior Windows tests:
- PowerShell
\$HOME drift. \$HOME can resolve away from \$env:USERPROFILE under OneDrive Known Folder redirection, Git-for-Windows env, or group policy. Result: install lands in the wrong .claude tree, or two trees coexist on the same machine.
- Execution policy. Some users hit the unsigned-script prompt and don't know what to do; others can't change policy because of group policy.
What we'd like:
- A clean walkthrough for the OneDrive-redirected case (largest share of business laptops).
- A non-interactive recipe that succeeds in CI or on a fresh user account.
- PRs welcome. Working through it on your own machine and pasting the gotchas you hit is also useful.
Reference: SCO pack hit the same \$HOME issue on Windows Server 2025 in 2026-05-01 (fixed by pinning to \$env:USERPROFILE); the same fix likely applies here.
The install notes assume File Explorer +
install.cmd. Two known rough edges from prior Windows tests:\$HOMEdrift.\$HOMEcan resolve away from\$env:USERPROFILEunder OneDrive Known Folder redirection, Git-for-Windows env, or group policy. Result: install lands in the wrong.claudetree, or two trees coexist on the same machine.What we'd like:
Reference: SCO pack hit the same
\$HOMEissue on Windows Server 2025 in 2026-05-01 (fixed by pinning to\$env:USERPROFILE); the same fix likely applies here.