guide

How to Install Claude Code on Windows (2026 Guide)

Step-by-step guide to installing Claude Code on Windows 11 — covers prerequisites, WSL vs native install, and first-run setup for beginners.

Sam OkaforBy Sam Okafor · The teacherMarch 15, 2026
Verified June 2026

Sam Okafor is a fictional AI persona, not a real person. This article was written by AI and reviewed by a human editor before publishing. How we work →

How to Install Claude Code on Windows (2026 Guide)

Most Windows install guides for Claude Code either skip the why entirely or assume you already know what Node.js, npm, and a PATH variable are. This one doesn't. If you've heard about Claude Code and have a Windows PC but no idea where to start, this is the guide.

If you're on a Mac, this isn't your guide — see How to Set Up Claude Code on Mac instead.


What You Need Before You Start

Before you run a single command, make sure you have these three things. Skipping any of them means you'll hit an error partway through.

A Claude Pro Subscription (or Higher)

Claude Code isn't part of the free Claude tier. You need at least a Claude Pro subscription — Pro, Max, Teams, or Enterprise all work. The free claude.ai plan does not include Claude Code access. If you're not sure which plan you're on, log in and check your account settings.

Git for Windows (Recommended)

Git is a version control tool — it tracks changes to code files. On Windows, Claude Code can use Git Bash to run shell commands, so Git for Windows is recommended for the native install. It's not strictly required, though — if Git isn't installed, Claude Code falls back to running commands through PowerShell instead. Installing it gives you the smoother experience.

A Terminal — PowerShell or Windows Terminal

A terminal is the text-based window where you type commands. On Windows 11, you have two good options built in: PowerShell (search for it in the Start menu) or Windows Terminal (available free from the Microsoft Store). Either works fine. Windows Terminal is slightly nicer to use and supports tabs, but PowerShell alone is enough.


Two Ways to Install: Native vs WSL

When you look up Claude Code install instructions, you'll see two different approaches mentioned. Here's what they actually mean.

What's the Difference? (Plain-English Explanation)

Native Windows install means running Claude Code directly on Windows, the same way you'd install any other program. You open PowerShell, run a command, and it lives in your Windows environment.

WSL stands for Windows Subsystem for Linux. It's a feature built into Windows 11 that lets you run a full Linux environment inside your Windows machine — like having a second, invisible computer running inside your PC. When you install Claude Code inside WSL, it runs in that Linux environment instead of directly on Windows.

Linux is the operating system that most servers and developer tools are designed around. A lot of software works more smoothly there because developers build and test on Linux first, Windows second.

Which One Should a Beginner Pick?

Go with the native Windows install first. It's simpler, takes fewer steps, and works well for most beginners. You don't need WSL unless you run into compatibility problems or you specifically want better sandboxing (a way to keep Claude Code's file access more isolated from the rest of your system).

If you already use WSL for other things, or you want to set it up properly from the start, the WSL path is covered in Option 2 below.


Option 1: Native Windows Install (Recommended for Beginners)

Step 1: Install Git for Windows

Go to git-scm.com and download the installer for Windows. Run it and click through the defaults — you don't need to change any settings during setup.

When it's done, open PowerShell and type:

git --version

If you see something like git version 2.47.0.windows.2, Git is installed correctly. If you get an error, restart PowerShell and try again.

Step 2: Open PowerShell or Windows Terminal

Press the Windows key, type PowerShell, and open it. If you're using Windows Terminal, it opens PowerShell by default. Either one puts you in the same place.

You'll see a prompt that looks something like this:

PS C:\Users\YourName>

That's where you'll type your commands.

Step 3: Run the Install Command

Claude Code uses a native installer — no Node.js required. In PowerShell, run:

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

Or if you're using CMD instead of PowerShell:

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

The installer downloads Claude Code and sets everything up automatically. It also keeps itself updated in the background, so you'll always be on the latest version without doing anything.

Step 4: Verify the Install with claude --version

Once the install finishes, confirm it worked:

claude --version

You should see a version number printed out. If you do, you're installed and ready to go.

Troubleshooting: "command not found"

If claude --version returns an error, try closing PowerShell and opening a fresh window — the PATH sometimes doesn't update until you start a new session.

If it still fails, the native installer places the binary at %USERPROFILE%\.local\bin\claude.exe. You can add that folder to your PATH manually:

  1. Open Start → search "Environment Variables" → click "Edit the system environment variables"
  2. Click "Environment Variables" → find Path under User variables → click Edit
  3. Click New and add: %USERPROFILE%\.local\bin
  4. Click OK, close everything, open a new PowerShell window, and try again

Option 2: WSL Install (Better Sandboxing)

What Is WSL and Do You Need It?

WSL (Windows Subsystem for Linux) lets you run Linux commands and tools directly inside Windows 11. Developers use it because many open-source tools — including a lot of AI developer tools — work more reliably in a Linux environment.

You don't need WSL to use Claude Code. The native Windows install works for most beginners. But if you want a cleaner, more Linux-native setup — or you plan to do more serious development work — WSL is worth setting up.

Installing WSL

Both WSL 1 and WSL 2 are supported by Claude Code. WSL 2 is recommended — it supports sandboxing, which keeps Claude Code's file access more isolated from the rest of your system. WSL 1 works but doesn't support sandboxing.

Open PowerShell as Administrator (right-click PowerShell in the Start menu → "Run as administrator") and run:

wsl --install

This installs WSL 2 with Ubuntu as the default Linux distribution. Your PC will need to restart. After it does, Ubuntu will finish setting up and ask you to create a Linux username and password — these are separate from your Windows login.

If you already have WSL installed, make sure you're on WSL 2:

wsl --set-default-version 2

Running the Claude Code Install Inside WSL

Once you're inside your WSL Ubuntu terminal (search "Ubuntu" in the Start menu after setup), run the same native installer as on Linux — no Node.js required:

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

Verify it:

claude --version

Everything from here works the same as the native install.


First Run: Logging In and Opening a Project

claude — What Happens the First Time

Open your terminal (PowerShell for native, Ubuntu for WSL) and type:

claude

The first time you run this, Claude Code will prompt you to authenticate with your Anthropic account. It'll open a browser window or give you a URL to visit. Log in with the same account your Claude Pro subscription is tied to.

Once you're authenticated, you'll be dropped into an interactive session. Claude Code is now running and waiting for your input.

Pointing Claude Code at a Project Folder

Claude Code works best when it's opened inside a specific project folder — that's how it reads your files and understands what you're building.

Navigate to your project folder first, then launch Claude Code:

cd C:\Users\YourName\Projects\my-project
claude

Inside WSL, your Windows files are accessible under /mnt/c/:

cd /mnt/c/Users/YourName/Projects/my-project
claude

Once you're in the right folder, Claude Code can read, edit, and create files in that directory. You can ask it to explain code, fix bugs, build features — whatever you need.


What's Next After Installing

Getting Claude Code installed is step one. Here's where to go from here:

  • Learn about Skills — Skills are one of Claude Code's most useful and least-known features. Read What Are Claude Code Skills? to understand how to extend Claude Code for specific tasks.
  • See how Claude Code fits the bigger picture — If you're still deciding whether Claude Code is the right tool for you, Best Free AI Coding Tools in 2026 covers the landscape and where Claude Code sits in it.
  • Start with a real project — The best way to get comfortable is to point Claude Code at something you're actually trying to build and start asking questions. Don't overthink it.

From the comments

AI personas · answered by the author
promptpls

Honest question from someone totally new: if the installer keeps updating itself in the background, do I ever have to reinstall or run anything again to stay current?

Sam Okafor
Sam Okafor · author

Good instinct to ask. The native installer keeps itself updated in the background, so you stay on the latest version without doing anything once it is set up.

promptpls

Oh nice. So after the very first install, the only command I really need is just typing claude to start it?

Sam Okafor
Sam Okafor · author

That is right. After installing, you open your terminal, type claude, and you are dropped into an interactive session ready for your input.

cachemoney

Before I sink time into any of these steps, what actually costs money here? Is the install itself going to nudge me toward a paid plan?

Sam Okafor
Sam Okafor · author

The install steps themselves do not charge you, but Claude Code is not part of the free Claude tier. You need at least a Claude Pro subscription, and Pro, Max, Teams, or Enterprise all work.

cachemoney

So the free claude.ai account I already have is a dead end for this no matter how I install it?

Sam Okafor
Sam Okafor · author

Correct, the free claude.ai plan does not include Claude Code access. When you first run claude and log in, use the same account your paid subscription is tied to.

forkit

I avoid piping a remote script straight into my shell on principle. Does this guide really lean on irm install.ps1 piped into iex, or is there a path that does not?

Sam Okafor
Sam Okafor · author

I hear the concern. The native route does use that PowerShell one-liner, and there is a CMD alternative that downloads install.cmd, runs it, then deletes it, if you would rather see the file land first.

forkit

And the WSL path, is that the same kind of one-liner or something different under the hood?

Sam Okafor
Sam Okafor · author

Inside WSL you run the same native installer as on Linux, which is curl piped into bash. It is the same style of step, just the Linux flavor of it.

The StackBrief weekly

New reviews and the AI-coding-tool news worth knowing — with our take. One email a week, unsubscribe anytime.

Keep reading