How to Install Claude Code on Windows, macOS and Linux

Claude Code now has native installers for Windows, macOS and Linux. You do not need to install it globally through npm for the standard setup.

The installation itself is the easy part. The work that protects a business comes next: verify the binary, authenticate with the intended account, start in a controlled repository and tell Claude which commands and boundaries apply.

These steps follow Anthropic's current Claude Code installation guide. Check that page if a command or system requirement changes.

Before you install Claude Code

Anthropic currently lists these baseline requirements:

• macOS 13 or later;
• Windows 10 version 1809 or later, or Windows Server 2019 or later;
• Ubuntu 20.04+, Debian 10+ or Alpine 3.19+;
• at least 4 GB of RAM;
• an x64 or ARM64 machine;
• network access and an Anthropic or supported cloud-provider account.

Git for Windows is recommended on native Windows. In a company environment, confirm that local shell tools and model access fit your security policy before connecting Claude to a real codebase.

Install Claude Code on Windows PowerShell

Open PowerShell and run:

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

Then open a fresh terminal and verify the command:

powershellclaude --version

If you prefer Command Prompt, Anthropic also documents a Windows install.cmd route. Use the official guide for the current command.

If PowerShell says claude is not recognised, close and reopen the terminal first. Then check whether the installer directory is on PATH. Do not solve a path problem by repeatedly installing different copies.

Install Claude Code on macOS or Linux

Run the native installer:

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

Open a new shell and verify it:

bashclaude --version

On managed machines, review downloaded scripts according to your organisation's software policy before running them.

Authenticate the intended account

Start Claude Code:

textclaude

Follow the browser authentication flow. The available account and billing routes can change, so use Anthropic's current product documentation rather than a fixed plan list copied into an article.

In a company environment, make the account boundary explicit:

• which organisation owns the account;
• which repository or project it may access;
• where usage is billed;
• who can revoke access;
• whether prompts or tool output can contain personal or confidential data.

Verify the installation safely

Do not make the first test “fix everything in this repository”. Create or open a small test project and ask for a read-only inspection:

textSummarise this repository's purpose and list its available test commands.
Do not edit files or run commands.

Check that Claude:

1. opened the intended directory;
2. described the files accurately;
3. respected the no-edit instruction;
4. asked before any action that required permission.

Then try one reversible change on a branch and inspect the diff yourself.

Add project instructions

Claude Code can use a CLAUDE.md file for repository-specific guidance. Keep it short and operational. Link to deeper documentation instead of duplicating it.

markdown# Project

- Install: `npm ci`
- Test: `npm test`
- Build: `npm run build`

## Boundaries

- Work on a branch.
- Do not change production data.
- Do not commit secrets or `.env` files.
- Ask before deployment or external messages.

## Conventions

- Reuse existing components and utilities.
- Add the smallest test that protects non-trivial logic.
- Preserve unrelated changes in a dirty worktree.

Instructions should describe facts that are true for the repository. They cannot replace operating-system permissions, access control or human review.

Common installation problems

claude is not recognised on Windows

Open a new terminal, then inspect PATH and the install location. Avoid keeping both an old npm installation and a native installation unless you have a specific reason.

The native binary is not installed

Run the current native installer again after checking the official prerequisites. If an older package-manager installation is intercepting the command, identify which executable is running before removing anything.

On PowerShell:

powershellGet-Command claude -All

On macOS or Linux:

bashcommand -v -a claude

Browser authentication opens the wrong account

Sign out of the unintended account or use a separate browser profile. Verify the organisation and billing context before accepting access.

Claude opens the wrong project

Exit, change to the intended directory and start again. Repository context is a boundary, not a cosmetic detail.

Company proxy or certificate errors

Use your organisation's supported proxy and certificate configuration. Do not disable TLS verification to make installation pass.

What to add next

Add capability only from a real need:

• a CLAUDE.md for project facts and commands;
• a skill for a repeated, documented workflow;
• an MCP server for a necessary external system;
• a hook for a deterministic guard that prompts alone should not carry.

You do not need all four on day one.

Frequently asked questions

Does Claude Code require Node.js?

Not for the current native installation path. Older guides centred on the npm package are now stale.

Does Claude Code work in Windows PowerShell?

Yes. Anthropic provides a native PowerShell installer. Git for Windows is recommended for a complete development workflow.

Should I install Claude Code through npm?

Use the native installer unless Anthropic's documentation gives you a specific reason to choose another supported method.

Can I use Claude Code on a client repository?

Only with the repository owner's permission and appropriate data-handling controls. Start with the least access required and keep secrets outside source control.

Related reading

• What is Claude Code?
• Claude Code MCP servers
• Claude Code skills: write, share and govern

If installation is complete but the safe team workflow is not, Get unstuck.