Claude Code on Windows: pick native or WSL 2 by where your project lives

The guide's logic rests on a single trade-off. Sandboxed command execution is available only in WSL 2, so any developer who wants commands to run inside a sandbox is steered there regardless of where files sit. When that requirement is absent, the deciding factor becomes file location, and the troubleshooting notes explain why: touching files on the Windows filesystem from WSL slows disk reads, which can quietly reduce how many results Claude Code's search returns. The guide lists three fixes—move the project to the Linux home directory and launch claude there, narrow the search to specific folders or file types, or run natively on Windows when the working folder is on the Windows side. From these it derives an order of checks: first where the project lives, then whether a sandbox is needed. The install steps follow the same split—the shell command inside WSL, and a single PowerShell line for native Windows.