How to Install Claude Code on Windows, Mac & Linux (2026 Guide)

Learning how to install Claude Code takes about two minutes now — one command, one browser login, done. It didn't used to be this smooth: the old npm route needed Node.js and broke in creative ways on Windows. The current native installer is a self-contained binary that updates itself in the background. We've installed it on macOS, Ubuntu, Windows 11 (both PowerShell and WSL), and a Debian container this week to verify every command in this guide against the official docs. Here's the complete walkthrough, including the errors that trip people up.

System requirements (quick check)

• OS: macOS 13.0+, Windows 10 1809+ / Server 2019+, Ubuntu 20.04+, Debian 10+, or Alpine 3.19+
• Hardware: 4 GB+ RAM, x64 or ARM64 processor
• Shell: Bash, Zsh, PowerShell, or CMD
• Account: Claude Pro/Max/Team/Enterprise, or a Claude Console (API) account — the free plan doesn't include Claude Code (see our full pricing breakdown)

Install on macOS, Linux & WSL

Open a terminal and run:

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

That's the entire install. The script detects your platform, drops the binary in place, and sets up background auto-updates — you'll never manually update it. This same command works inside WSL on Windows, which is our preferred setup for Windows developers who live in a Linux toolchain.

Install on Windows (PowerShell or CMD)

In PowerShell:

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

In CMD:

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

The #1 Windows install mistake is running the wrong command in the wrong shell. The tell: your prompt starts with PS C:\ in PowerShell and plain C:\ in CMD. If you see "The token '&&' is not a valid statement separator" you're in PowerShell running the CMD command; if you see "'irm' is not recognized" you're in CMD running the PowerShell one.

Install Git for Windows too. Without it, Claude Code falls back to PowerShell as its shell tool instead of Bash, and plenty of dev workflows assume Bash. WSL users can skip this.

Homebrew, WinGet & Linux package managers

Prefer a package manager? brew install --cask claude-code tracks the stable channel (about a week behind, skips releases with regressions — honestly a feature), while claude-code@latest gets releases immediately. Windows has winget install Anthropic.ClaudeCode, and Debian/Fedora/RHEL/Alpine users get native apt/dnf/apk repos for fleet installs. One warning that bites people months later: package-manager installs don't auto-update — you own the upgrade cadence, so schedule it.

Verify, log in, and run your first session

Confirm the install worked:

claude --version

You should see a version number followed by (Claude Code). Then cd into any project and start it:

cd /path/to/your/project
claude

First run prompts a browser login — use your Claude subscription (recommended) or a Console account, which auto-creates a "Claude Code" workspace for cost tracking. Credentials are stored after that; /login inside a session switches accounts later. For your first prompt, try "what does this project do?" — Claude Code reads files as it needs them, no manual context required. Press Shift+Tab to cycle permission modes when you're ready to let it edit without asking every time.

Not a terminal person? VS Code, desktop app, and web

The CLI is just one surface. The VS Code extension (VS Code 1.98.0+) bundles its own copy of the CLI and adds inline diffs, @-mentions, and plan review — no separate install or API key needed, just sign in with your Claude account.

The desktop app goes further: parallel sessions with Git isolation, drag-and-drop panes, integrated terminal and file editor, and visual diff review. macOS gets a universal build, Windows has x64 and ARM64 installers, and Linux is in beta via apt/.deb packages.

There's also claude.ai/code in the browser, JetBrains IDE plugins, Slack, and CI integrations for GitHub Actions and GitLab. Same agent, same account, pick your surface.

Fixing the common install errors

Once you're installed and logged in, the real fun starts — our tips and tricks guide and the best skills directory are the fastest ways to level up, and if you're weighing costs, the pricing guide covers which plan your usage actually needs.

Frequently Asked Questions