Claude Code Download for Windows: Desktop, CLI or WSL?

When searching for Claude Code download, the most common pitfall isn't download failure, but not first figuring out which one you need to install:

• If you want a graphical interface and side-by-side management of multiple tasks, download Claude Desktop and go to the Code tab;
• If you want to type claude in PowerShell, CMD, Git Bash, or an IDE terminal, install Claude Code CLI;
• If your projects and toolchains mainly run on Linux, or you need a sandbox, install into WSL 2;
• Desktop and CLI can be installed together; they are not mutually exclusive options.

This article is compiled from official documentation as of August 2026. There are only two official download entry points:

• Claude official download page
• Claude Code official installation docs

Do not download so-called "Claude Code installer packages" from cloud drives, software download sites, or unfamiliar GitHub Releases.

First, the verdict: Claude Code Desktop, CLI, or WSL - how to choose

The simplest way to decide:

• If it's your first time with Claude Code, install Desktop first;
• If you're already used to a terminal, install CLI directly;
• If your development environment is already in WSL, don't mess with cross-file-system setups; install straight into WSL 2.

Claude Code Desktop App Download and Installation

The desktop version of Claude Code is not a standalone product named "Claude Code.exe". It lives in the Code tab inside the Claude Desktop app.

Step 1: Choose your version from the official download page

Open claude.com/download, Windows users choose by processor:

• Most Intel / AMD PCs: download Windows x64;
• Windows on ARM devices: download Windows ARM64.

After installation, launch Claude from the Start menu, sign in to your Anthropic account, then click Code at the top.

Step 2: Choose a runtime environment

When you create a new Code session, the desktop version typically offers three environments:

• Local: directly reads and modifies projects on this computer;
• Remote: runs in Anthropic's cloud environment;
• SSH: connects to remote Linux or macOS machines you manage.

If you just want Claude to modify a local project, choose Local, then select the project folder. Windows local sessions need Git; install Git for Windows first.

Who is the Desktop version for?

The advantage of Desktop isn't "wrapping a terminal in a window"; it puts multi-session, file editor, terminal, Diff review, app preview, and PR status in one interface. You can run multiple Agents side by side without constantly switching terminal tabs.

But if you need scripted startup, work in an existing terminal, or frequently use slash commands, the CLI is usually more direct.

Claude Code Desktop requires a Pro, Max, Team, or Enterprise plan. If you've installed the app but can't see Code, first check your signed-in account and subscription permissions.

Claude Code CLI: Native Windows Installation

The official recommendation now is the native installer; you no longer need to install Node.js globally just for Claude Code.

Method 1: Install via PowerShell (recommended)

Open PowerShell and run:

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

After installation, close and reopen the terminal, then verify:

claude --version
claude

The first time you run claude, it will guide you through signing in. Enter your project directory before starting it so it can read code from the correct working directory:

cd D:\Projects\my-app
claude

Method 2: Install via WinGet

If you're used to the Windows package manager:

winget install Anthropic.ClaudeCode

The WinGet version won't auto-update in the background like the native installer; you'll need to run manually later:

winget upgrade Anthropic.ClaudeCode

Method 3: Install via CMD

If your prompt is C:\Users\...> without a preceding PS, you're using CMD. Run:

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

PowerShell and CMD commands can't be mixed. Many "install script syntax errors" are essentially just pasting a CMD command into PowerShell, or vice versa.

Claude Code on Windows: Native or WSL 2?

Claude Code already supports native Windows; it's no longer "Windows must install WSL". But each environment has trade-offs.

Choose native Windows if:

• Your projects are on C:\ or D:\;
• You rely on native tools like Visual Studio, PowerShell, Windows SDK;
• You want the simplest installation;
• You don't need the Claude Code sandbox.

In native mode, Git for Windows is recommended. Claude Code will prefer Git Bash to execute the Bash tool; if Git Bash isn't available, it can also use the PowerShell tool.

Choose WSL 2 if:

• Your projects are mainly Linux, Docker, Node/Python server-side toolchains;
• You need the sandbox;
• Your deployment environment is Linux;
• You've been developing in the WSL terminal for a long time.

Once inside WSL 2, run the Linux installation command:

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

Then verify inside WSL:

claude --version
claude

Don't start from Windows PowerShell one moment and WSL the next, expecting paths, Git, and environment variables to be identical on both sides. Install and run Claude Code in the same environment where your project lives.

What's the difference between Claude Code Desktop App and CLI?

A practical combo: use Desktop on a daily basis to view multiple sessions and diffs, and switch to CLI when you need automation or terminal context. Installing the CLI doesn't affect the Desktop's Code tab.

Common Windows Installation Errors

1. `The token '&&' is not a valid statement separator`

You pasted a CMD command into PowerShell. Go back to the PowerShell method above and use:

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

2. `'irm' is not recognized`

You're currently using CMD, not PowerShell. Open Windows PowerShell, or use the CMD installation command instead.

3. `claude` is not recognized as an internal or external command

First close and reopen the terminal. If it still can't be found, check whether %USERPROFILE%\.local\bin is in your PATH, then run:

Get-Command claude

You can also run the official diagnostic:

claude doctor

4. Git Bash not found

Install Git for Windows; if it's in a custom directory, you can specify it in Claude Code settings:

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

5. No Code tab in Desktop, or a 403 appears

Check in order:

1. Whether the currently signed-in account is the one that purchased a Claude plan;
2. Whether Claude Desktop is updated to the latest version;
3. Sign out, restart the app, and sign back in;
4. Whether the team account has Claude Code restricted by an administrator.

After Installation: How to Continue Claude Code from Your Phone or Browser

Installation answers "where Claude Code runs"; remote control answers "how to continue when you're away from the computer".

Anthropic already offers official options like Desktop, Web, Remote Control, and mobile Dispatch. If you only use an official Claude account and official models, you should usually try these features first.

If you also need the following scenarios, consider PandaNpc:

• Remotely control Claude Code, OpenAI Codex, and PandaCode from the same interface;
• Agents keep running on your own Windows / macOS / Linux dev machines;
• Use custom models or your own API endpoint;
• Continue the same session from an iPhone, any browser, another desktop computer, or a Chrome sidebar;
• Remotely watch streaming output, approve tool calls, answer questions, and view code changes;
• No public ports are opened; both the dev machine and controller only establish outbound connections.

First make sure the official Claude Code works correctly, then install pandapaw on the dev machine:

Windows PowerShell:

iwr -useb https://cos.pandanpc.com/pandapaw/install.ps1 | iex

macOS / Linux:

curl -fsSL https://cos.pandanpc.com/pandapaw/install.sh | sh

After installation, open PandaNpc Agent; connections from your dev machine will appear in the list. You can also use the Windows / macOS / Linux client or iOS App.

FAQ

Is Claude Code a desktop app or a command-line tool?

Both. The Code tab in Claude Desktop provides a GUI; Claude Code CLI starts from the terminal. They serve different workflows and can be installed together.

Does Claude Code on Windows require WSL?

Not required. Native Windows is supported. For Windows projects, prefer native installation; choose WSL 2 for Linux toolchains or when you need the sandbox.

Does Claude Code download require Node.js?

Desktop doesn't. The official native CLI installer doesn't either. Node.js is only needed if you're still using the old npm install -g @anthropic-ai/claude-code method.

Is there a Windows ARM64 version of Claude Code?

The official Claude Desktop download page provides a Windows ARM64 installer. For the CLI, go by the platform currently recognized by the official installation script.

Does Claude Code Desktop support Linux?

Claude Code's desktop Code experience is currently available for macOS and Windows. Linux users use the CLI, or operate sessions running on Linux via Web / remote clients.

Which is better: Desktop or CLI?

There's no absolute answer. Choose Desktop for visual, multi-session, Diff, and preview needs; choose CLI for terminal efficiency, scripting, and existing dev toolchains; prioritize WSL 2 for Linux environments and sandbox needs.

One-Sentence Summary

If you just want to get started quickly: install Desktop from the Claude official download page and open the Code tab.

To use it in a Windows terminal: run in PowerShell:

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

If your projects are in a Linux toolchain: enter WSL 2 and run:

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

First install the official Claude Code correctly, then decide whether you need Desktop and CLI together, and whether you need PandaNpc to remotely continue sessions from your phone, browser, or another computer.