Claude Code on Windows: native vs WSL, what actually works.

The short answer

• Go native if

  Your project sits on your Windows drive and you use Windows tools. It's simpler, and file access is faster.

• Pick WSL if

  Your project already uses Linux tools, or you want Claude Code's sandboxing, which only works on WSL 2.

1Route 1: native Windows

1. Run Anthropic's native installer. It's the recommended way. In PowerShell:
   PowerShell

   irm https://claude.ai/install.ps1 | iex

   In Command Prompt (CMD) it's a different command:
   Command Prompt (CMD)

   curl -fsSL https://claude.ai/install.cmd -o install.cmd && install.cmd && del install.cmd

2. Open a new terminal and check it.
   PowerShell or CMD

   claude --version

Two other ways to install

• WinGet

  winget install Anthropic.ClaudeCode works, but it doesn't update itself; run winget upgrade Anthropic.ClaudeCode now and then.

• npm

  npm install -g @anthropic-ai/claude-code needs Node.js 22 or later and installs the same native program.

2Route 2: WSL

WSL (Windows Subsystem for Linux) runs a real Linux system on Windows. It needs Windows 10 version 2004 (build 19041) or later, or Windows 11.

1. Install WSL once, from PowerShell opened as Administrator, then restart:
   PowerShell (Administrator)

   wsl --install

2. Open Ubuntu, which that installs under WSL 2.
3. Install Claude Code with the Linux installer, inside WSL, not from PowerShell:
   Ubuntu (WSL)

   curl -fsSL https://claude.ai/install.sh | bash

WSL setups don't need Git for Windows.

Where WSL is better

• Linux toolchains

  If your project builds with Linux tools, Claude Code runs them as they are.

• Sandboxing

  Claude Code's sandboxed command running works on WSL 2, not on WSL 1 or native Windows.

What it costs you

• Two file systems

  Your Windows C:\ drive shows up in Linux as /mnt/c. Microsoft recommends keeping a project on the side you work from: in WSL, under /home/<you>/, not /mnt/c/. Working across the two is slower.

• Paths look different

  C:\Users\you\Project is /mnt/c/Users/you/Project in WSL. To see WSL files from Windows, type \\wsl$ in File Explorer, or run explorer.exe . in a WSL folder.

• Two of everything

  Git, Node.js and your settings live separately on each side. Microsoft's own advice: install Git on each file system you use it from.

• Sign-in can need a paste

  In WSL 2 the browser may not redirect back after you sign in. It shows a code instead; paste it into Claude Code.

Native vs WSL at a glance

Common problems and fixes

$currentPath = [Environment]::GetEnvironmentVariable('PATH', 'User')
[Environment]::SetEnvironmentVariable('PATH', "$currentPath;$env:USERPROFILE\.local\bin", 'User')

{ "env": { "CLAUDE_CODE_GIT_BASH_PATH": "C:\\Program Files\\Git\\bin\\bash.exe" } }

Where Technically Not fits

Technically Not is a desktop app for Windows 10 and 11 (and Linux) that runs the coding agents you already use side by side, with live status. It uses the native route: it finds claude on your Windows PATH, the same way your terminal does, and starts it in a real terminal panel in your project folder. If Claude Code isn't signed in yet, that panel runs its sign-in first.

• Real terminals

  Each panel is a real Windows console running the CLI itself, or Windows PowerShell for a plain terminal. Up to 12 panels per workspace.

• Next to other agents

  Codex, Cursor Agent and OpenCode run in their own panels beside Claude Code. See how to run Claude Code and Codex together.

• More than one account

  Keep several Claude Code accounts signed in and switch when one hits its limit. How account switching works.

Questions

Sources

Technically Not is an independent app and isn't affiliated with Anthropic.