Claude Code and Codex on Windows: native or WSL, and what still breaks
Both tools change fast; we re-check this page regularly.
Claude Code on Windows runs natively today, and so does Codex. You no longer need WSL just to start them, and many older guides that say otherwise are out of date. The harder part on Windows is what comes next: running the apps the agent builds, which are often written with Mac and Linux in mind.
The short answer
- Just want to try it? Install natively. It’s the fastest start.
- Building real web apps with databases, or want the agent to work with fewer approval prompts? Use WSL2, or a tool that sets it up for you.
Claude Code on Windows
Native: install it from PowerShell or CMD; no administrator rights needed. It runs on Windows 10 (version 1809) or later. Git for Windows is optional: with it, Claude Code uses Git Bash for shell commands; without it, it uses PowerShell. If you’d rather avoid the terminal entirely, Anthropic’s desktop app includes Claude Code.
WSL2: you install and run Claude Code inside the Linux environment, using the Linux installer.
The difference that matters most: Claude Code’s sandbox works in WSL2 but not on native Windows. The sandbox lets the agent run commands within set boundaries without asking you every time. On native Windows, each command you approve runs with your full user account’s access.
Official setup instructions: Claude Code docs.
Codex on Windows
Codex comes as a Windows app, a CLI and an IDE extension. By default the agent runs natively and uses a Windows sandbox that blocks writes outside the project folder and network access until you approve them. In the app’s settings you can switch the agent to WSL2 instead (restart the app after switching).
One trap if you go the WSL route: keep your project inside the Linux file system. Working from a Windows drive through /mnt/c/... is noticeably slower.
Official setup instructions: Codex on Windows.
Native vs WSL2 at a glance
| Native Windows | WSL2 | |
|---|---|---|
| Setup | One install command or app | Enable WSL, possibly a restart, then install inside Linux |
| Claude Code sandbox | Not supported | Supported |
| Codex sandbox | Windows sandbox | Linux sandbox |
| Projects written for Mac/Linux | Often need fixes | Usually run as-is |
| Databases and services | Separate Windows installs; some only recommend WSL | Same commands as most tutorials |
| Where your files live | Normal Windows folders | Inside Linux; keep them there for speed |
What still breaks on Windows
The agent itself runs fine. The friction is in the projects:
- Scripts written for Mac and Linux. Projects often include start scripts and commands that assume a Linux-style shell. On native Windows the agent has to translate them, and sometimes gets it wrong.
- Databases and background services. Tutorials and agents tend to reach for tools like PostgreSQL or Redis. On Windows each one is a separate install, and some, Redis for example, officially point Windows users to WSL.
- Live reload across the boundary. If the code lives in a Windows folder but runs inside WSL, the “save the file, page refreshes” loop can stop working, and everything feels slower.
- WSL itself. It needs virtualization enabled in the BIOS, sometimes a restart, and occasionally hangs after sleep. The usual fix is
wsl --shutdown, which also stops every other Linux environment you have.
None of this is hard for a developer. For someone vibe coding on Windows who just wants to describe an app and see it, it’s where the afternoon goes.
The easier way: let Eggie set it up
Eggie sets up a ready-made Linux workspace on your Windows PC (WSL2 under the hood) and manages it for you:
- One installer. If WSL was never enabled, Eggie asks once, you restart, and setup continues on its own.
- Projects live inside Linux, where Mac/Linux-style projects run as they are and stay fast.
- Running is a button. Each project gets its own address, Start/Stop and Open in browser. See how to run an app your agent built.
- Bring your own agent: Claude Code, Codex or Cursor, the one you already pay for.
FAQ
Do I need WSL to use Claude Code on Windows?
No. Claude Code installs natively from PowerShell or CMD. WSL2 is optional, but it’s the only way to use Claude Code’s sandbox on Windows.
Is the Codex app or the Codex CLI better on Windows?
If you don’t live in the terminal, start with the app. Both use the same sandbox options and the same account.
Why is my project so slow in WSL?
It’s probably stored on the Windows drive and accessed through /mnt/c. Move it into your Linux home folder and open it from there.
Can I use Cursor on Windows?
Yes, Cursor runs on Windows. The same rule applies to the apps it builds: projects that assume Mac or Linux run more smoothly inside WSL2.