Why Claude Code Is Not Supported on Windows and What You Can Do Instead

You’re staring at your PowerShell terminal, ready to unleash Anthropic’s new powerhouse, but the installation fails. It's frustrating. You’ve probably seen the buzz around Claude Code, the agentic command-line tool that basically acts as a pair programmer living inside your terminal. It can research, fix bugs, and commit code. But there is a massive catch for a huge chunk of the developer population: Claude Code is not supported on Windows. If you try to run the install command on a native Windows environment, you’re going to hit a wall.

It feels like a snub. Why would a major AI player ignore the world’s most popular desktop OS? It isn't actually a snub, though. It’s a technical limitation based on how the tool was built. Claude Code relies heavily on Unix-style file systems and terminal behaviors. Windows, with its backslashes and different way of handling process signals, just doesn't play nice with the initial beta release. Anthropic is being honest about it. They built this for macOS and Linux first because that's where the "agentic" architecture is easiest to stabilize.

📖 Related: The First Photograph Ever Taken: What Actually Happened in 1826

If you're on Windows 11 or 10, don't throw your laptop out the window yet. You have options.

The Reality of Why Claude Code Is Not Supported on Windows

Software development isn't always "write once, run anywhere." Claude Code is a specialized CLI tool. It needs to interact with your local file system, run git commands, and manage shell environments autonomously. Because it uses Node.js, you might think it would be cross-platform by default. It's not. The way Claude Code monitors file changes and executes shell sub-processes is currently hard-coded for POSIX-compliant systems.

Basically, the "plumbing" of Windows is different. While macOS and Linux share a common lineage in how they handle terminal commands, Windows uses the NT kernel. Even with PowerShell getting better every year, the underlying logic for how a program "takes control" of a terminal—which Claude Code needs to do to be an agent—is fundamentally different.

Honestly, it’s a beta. Anthropic released this to get feedback from the "hacker" community, and that community leans heavily toward macOS and Linux. They’ll likely fix this eventually. But right now? You’re stuck if you’re trying to run it directly in cmd.exe.

Your Secret Weapon: WSL2

If you’re a Windows dev and you aren't using WSL2, you're missing out anyway. This is the only real way to bypass the fact that Claude Code is not supported on Windows natively. WSL2 (Windows Subsystem for Linux) allows you to run a literal Linux kernel inside Windows. It isn't an emulator. It’s a lightweight utility that gives you the best of both worlds.

To get Claude Code running, you need to set up a Linux distribution like Ubuntu from the Microsoft Store. Once you’re inside that terminal, Claude Code thinks it’s on a Linux box. It works perfectly. You’ll need to make sure you have Node.js version 18 or higher installed inside the WSL environment, not just on your Windows host.

A lot of people make the mistake of installing Node on Windows and then wondering why their WSL terminal can't find it. Keep them separate. Use nvm (Node Version Manager) inside your Ubuntu terminal to get the right version. Then, run the npm install command for Claude Code. It works like a charm. You can even access your Windows files from within WSL by navigating to /mnt/c/.

Setting Up the Environment

1. Open PowerShell as Admin and run wsl --install.
2. Restart your computer. Seriously, do it.
3. Open the newly installed Ubuntu app.
4. Update your packages: sudo apt update && sudo apt upgrade.
5. Install Node.js (v18+).
6. Run npm install -g @anthropic-ai/claude-code.

What About Claude Code in VS Code?

You might be thinking, "Can't I just use the Claude Dev extension?" Well, that's different. There’s a distinction between the "Claude Code" CLI tool from Anthropic and various third-party extensions like Cline (formerly Claude Dev). Those extensions do work on Windows because they operate through the VS Code API.

But if you want the official Anthropic CLI experience—the one that has that specific "agentic" loop—you have to stick to the CLI path. The CLI is designed for a specific type of workflow where you never leave the terminal. It feels faster. It feels more raw.

If WSL2 sounds like too much work, your only other real option is a Dev Container or a cloud-based environment like GitHub Codespaces. Since Codespaces runs on Linux VMs, Claude Code will install there without a single complaint. It’s a great way to test the tool without messing up your local machine’s configuration.

The Performance Gap and File Systems

Here is a nuanced point most people miss: even if you get it running in WSL2, you should keep your code files inside the Linux file system. If you try to run Claude Code in WSL but your project files are sitting on your Windows C: drive, it will be slow. Painfully slow.

The translation layer between the Linux kernel and the Windows NTFS file system is a bottleneck. For the best experience, clone your repositories directly into your WSL home folder (e.g., ~/projects/my-app). Claude Code will be able to index your files and perform git operations significantly faster. It’s the difference between a tool that feels like magic and one that feels like a chore.

Is a Native Windows Version Coming?

Anthropic hasn't given a specific date. They’ve acknowledged the demand, though. In the world of high-end AI tools, Windows support often lags behind because many AI researchers and engineers work exclusively on Mac or Linux.

🔗 Read more: Free Online Data Science Courses: Why Most People Fail and How to Actually Get Hired

We saw this same pattern with early versions of many Python-based AI libraries. Eventually, the demand from enterprise developers—who are often tethered to Windows laptops for security or corporate policy reasons—forces a native port. Expect it, but don't wait for it. The current workaround via WSL2 is so robust that it might be the "official" recommendation for a long time.

Moving Forward with Claude Code

Since Claude Code is not supported on Windows in a native capacity, your path forward is clear. You either embrace the Linux subsystem or you wait on the sidelines. Given how fast the AI space moves, waiting is usually the wrong move.

• Check your hardware: WSL2 needs virtualization enabled in your BIOS. If you get a "Virtualization not enabled" error, you’ll need to poke around your motherboard settings.
• Manage your API keys: You’ll need an Anthropic API key with a positive balance. This isn't free. It’s a professional tool that consumes tokens as it thinks and writes.
• Use the TUI: Once installed, run claude and explore the Terminal User Interface. It’s surprisingly intuitive for a command-line tool.
• Keep it updated: Since this is a beta, run npm install -g @anthropic-ai/claude-code frequently to grab the latest bug fixes.

Getting Claude Code running on a Windows machine requires a few extra steps, but the payoff is worth it. You're basically getting a senior engineer who lives in your terminal and doesn't complain about technical debt. Just give it the Linux environment it craves, and it'll work wonders for your productivity.