I’ll be straight with you when I first heard Anthropic’s terminal-based AI coding assistant was coming to Windows, I figured it would be Underdeveloped. Most developer tools treat Windows like a secondary platform. The Claude Code install Windows experience proved me wrong.
If you’re completely new to the tool, it’s worth starting with a complete beginner’s guide to Claude Code before jumping into installation.
As of 2026, the setup is fast, the installer is polished, and you don’t need to be a developer to get it running. Whether you’ve used a terminal before or not, this guide covers every step system requirements, the actual install commands, account setup, and what to do when something goes sideways.
No assumptions. No skipped steps. Just the real process from start to finish.
System Requirements for Claude Code Install Windows
Before running anything, take two minutes to check your machine. I’ve watched people spend an hour troubleshooting an issue that was obvious from the start.
Here’s what you actually need:
- Operating system: Windows 10 version 1809 or newer, or Windows Server 2019+
- RAM: 4 GB minimum – 8 GB is more comfortable
- Internet connection: Required at all times – Claude Code talks to Anthropic’s servers. This dependency on cloud processing is tied to how Claude handles large projects using its context window, something explained in detail in this Claude Code context window guide.
- Shell: PowerShell, CMD, or Git Bash all work
- Git for Windows: Mandatory – not optional
That last one catches people off guard. Claude Code uses Git Bash internally to run commands on Windows. If you skip this, the install either fails entirely or behaves unexpectedly. Download Git for Windows first, then come back.
You also need a Claude.ai paid account – Pro, Max, Teams, or Enterprise. The free plan does not include Claude Code. Worth knowing before you spend 20 minutes on the install.
| Plan | Claude Code Access | Best For |
|---|---|---|
| Free | No | Basic Claude.ai chat only |
| Pro | Yes | Individual developers |
| Max | Yes | Heavy usage / power users |
| Teams / Enterprise | Yes | Organizations and teams |
Step-by-Step: How to Claude Code Install Windows
There are three supported installation methods. If you’re setting this up for real development workflows, you’ll eventually want to configure it properly using this Claude Code settings.json configuration guide. Here’s the honest comparison before I walk you through the recommended one.
The Best Claude Code Install Windows Method: Native PowerShell
The native installer is what Anthropic recommends and what I’d point anyone toward. It auto-updates in the background, requires no Node.js, and takes under a minute to run.
Open PowerShell – you do not need to run it as Administrator and paste this command:
irm https://claude.ai/install.ps1 | iexHit Enter. The installer downloads the binary, sets your PATH, and finishes silently. That’s the whole thing.
If you prefer Windows CMD, the equivalent command is:
curl -fsSL https://claude.ai/install.cmd -o install.cmd && install.cmd && del install.cmdSame result, but with different syntax. Use whichever shell you’re more comfortable with.
After the install finishes, verify it worked:
claude --versionIf a version number appears, you’re good. If you get a “command not found” error, close your terminal completely, reopen it, and try again. PATH changes sometimes need a fresh shell session to take effect.
WinGet and npm: When to Use Them
WinGet works fine if you prefer managing software through Windows Package Manager.
winget install Anthropic.ClaudeCodeThe catch it doesn’t auto-update. You’d need to run winget upgrade Anthropic.ClaudeCode manually whenever a new version drops.
npm installation is officially deprecated. Anthropic still supports it for legacy setups, but I’d avoid it entirely for anything new. The native installer is faster, lighter, and better supported.
Staying on the Claude Code Latest Version
One of my favorite things about the native install is that you don’t have to think about updates. The claude code latest version gets downloaded in the background while you’re working and applies the next time you start a session.
If you want to force an update right now say you just heard a new feature shipped – run:
claude updateThat pulls the newest build immediately without waiting for the automatic check.
You also have control over your update channel. The default is latest, which gives you new features as soon as they’re released. If you’d rather stay on something more tested, switch to stable – it runs about a week behind and skips releases with major bugs.
You can change the channel through /config inside Claude Code, or add it manually to your settings.json:
"autoUpdatesChannel": "stable"For most people, staying on latest is fine. The stable channel is more useful for teams or anyone running Claude Code in a production-adjacent environment where unexpected behavior matters more.
Signing In and Running Your First Command
Once the installation is complete, type claude in your terminal and press Enter.
This will open an authentication prompt in your browser. Log into your Anthropic account, confirm the connection, and you’re in. The whole auth flow takes about 30 seconds.
Back in the terminal, Claude Code is ready. Once you’re inside, the real power comes from how you use it, especially features like agent mode and task execution, which are covered in this Claude Code dispatch guide. You can point it at a project folder, ask it to read and explain a file, generate code, or run tasks. You can do all of this using plain English typed directly into the terminal.
For anyone downloading Claude code for the first time, it is important to understand that this isn’t a desktop app with a graphical interface. It’s a terminal tool. If you’re not comfortable working in terminal-based environments, you might also want to compare it with tools like Cursor vs Claude Code to see how different workflows feel. Once you get that, the workflow becomes easy. Start with something small. Ask it to explain one file in a real project. That first response usually helps clear up any confusion.
When the Install Goes Wrong
Most Windows installs go smoothly. A few issues come up often enough to mention.
Git Bash not found: If Claude Code installed but can’t locate Git, add this to your settings.json manually:
"CLAUDE_CODE_GIT_BASH_PATH": "C:\\Program Files\\Git\\bin\\bash.exe"Adjust the path if your Git installation is located somewhere else.
Authentication loop: Occasionally the browser auth gets stuck, usually due to strick cookie or tracker-blocking settings. Try a different browser for the initial login, or temporarily disable tracking protection during setup.
PATH issues after install: If claude --version still fails after restarting your terminal, check that %USERPROFILE%\.local\bin is in your system PATH. The installer adds it, but some environments may not recognize it right away.
If you’re stuck, run claude doctor from your terminal. It performs a full diagnostic check environment, config, network and tells you exactly what’s misconfigured.
One of the most common issues developers run into is the setup failure. Here’s how to fix the Claude Code process exited with code 1 error.
What to Do Next After the Claude Code Install on Windows
The Claude Code install Windows process is genuinely one of the seamless setups I’ve done for a developer tool in recent memory. Install Git for Windows, run the PowerShell one-liner, authenticate, and you’re working. Five minutes total on a normal connection.
Here’s my honest suggestion for what to do next: navigate into an actual project you’ve been working on and ask Claude Code to walk you through one of the files. Not a tutorial project. Your project. Watching it read your own code and respond logically is a different experience than any demo.
The claude code latest version handles itself. Updates come automatically. Authentication renews when needed. What’s left is just learning how to ask good questions in the terminal and that part gets easier every session.
If you want to go beyond basic usage and automate workflows, learning Claude Code hooks for task automation can significantly improve your productivity.
Frequently Asked Questions
Do I need Git for Windows if I’m already using WSL?
Good question and the answer is no, not if you’re running Claude Code inside a WSL session. WSL 1 and WSL 2 are both fully supported, and inside those environments you’d use the Linux-style install command instead. The Git for Windows requirement only applies when you’re running Claude Code directly in native Windows shells like PowerShell or CMD. If you already have WSL set up and you’re comfortable using it, installing Claude Code there is a perfectly valid option. WSL 2 also supports sandboxing for extra security, which WSL 1 doesn’t. Either way, you don’t need both, pick the environment you’re more comfortable in and stick with it.
Can I run multiple versions of Claude Code on the same Windows machine?
Not easily, and honestly not recommended. The native installer manages one binary at %USERPROFILE%\.local\bin\claude and updates it in place. If you genuinely need version pinning. Say you’re working in an environment where unexpected updates would cause problems you can install a specific version by passing a version number to the install script and then disabling auto-updates entirely through your settings.json. Set DISABLE_AUTOUPDATER to "1" in the env block. That freezes Claude Code at whatever version you installed until you manually run claude update or re-run the installer with a different version number.
Is there a desktop app option instead of the terminal?
Yes, actually. Anthropic released a desktop app for both macOS and Windows that lets you use Claude Code without ever touching a terminal. For Windows, you can grab it directly from the Claude.ai downloads page. It’s a good option if the terminal feels uncomfortable, but I’d argue learning the terminal version is worth it you get more control, better scripting capability, and the experience transfers to other tools. The desktop app and the claude code download windows terminal version use the same core engine, so you’re not missing features by choosing one over the other.
What happens to my Claude Code settings if I need to reinstall?
Your configuration and session history live separately from the binary in %USERPROFILE%\.claude. Uninstalling or reinstalling Claude Code doesn’t touch that folder, so your settings survive. If you want a genuinely clean reinstall wiping everything including tool permissions and history you’d need to delete that folder manually after removing the binary. Just back up your settings.json first if you have custom configurations you want to keep. It takes about 30 seconds to set up again from scratch, but losing a carefully tuned config is annoying when it’s avoidable.