How do I install Claude Code, and how do I keep it updated?

Short answer

Run the native installer: curl -fsSL https://claude.ai/install.sh | bash on macOS, Linux and WSL, or irm https://claude.ai/install.ps1 | iex in Windows PowerShell. Then run claude in your project and log in with a paid Claude plan or a Console account. Native installs update themselves, npm installs too when the npm folder is writable; Homebrew and WinGet need manual upgrades by default.

The install command for your system

Claude Code runs on macOS 13 or later, Windows 10 1809 or later (or Windows Server 2019), Ubuntu 20.04, Debian 10 and Alpine 3.19 or later, with at least 4 GB of RAM on x64 or ARM64. These are the install routes in the docs as of November 2026:

Route Command Updates
Native, macOS, Linux, WSL curl -fsSL https://claude.ai/install.sh | bash Automatic
Native, Windows PowerShell irm https://claude.ai/install.ps1 | iex Automatic
Native, Windows CMD curl -fsSL https://claude.ai/install.cmd -o install.cmd && install.cmd && del install.cmd Automatic
Homebrew brew install --cask claude-code Manual
WinGet winget install Anthropic.ClaudeCode Manual
apt, dnf, apk Signed repositories from downloads.claude.ai Through your system upgrades
npm npm install -g @anthropic-ai/claude-code@latest Automatic if the npm folder is writable

Anthropic recommends the native installer. After it finishes:

  1. Open a new terminal and run claude --version. A version number means it worked. “Command not found” means the install folder is not on your PATH yet.
  2. Go to your project and run claude. A browser window opens to log in. You need a Pro, Max, Ultra, Team, Enterprise or Console account; the Free plan does not include Claude Code.
  3. Check the setup with claude doctor if anything feels off. It prints install health, settings errors and the result of the last update attempt without starting a session.

Prefer no terminal at all? The Claude desktop app includes Claude Code in its Code tab, so you do not need the CLI for that route. See desktop vs CLI vs web.

Windows: native, WSL 2 or WSL 1

Option Needs Sandboxing Use it for
Native Windows Nothing; Git for Windows optional Not supported Windows projects and tools
WSL 2 WSL 2 enabled Supported Linux toolchains, sandboxed commands
WSL 1 WSL 1 enabled Not supported Only if WSL 2 is unavailable

On native Windows you run the PowerShell or CMD command; no Administrator rights needed. With Git for Windows installed, Claude Code uses Git Bash for its Bash tool. Without it, Claude Code runs shell commands through its PowerShell tool. If it cannot find Git Bash, set CLAUDE_CODE_GIT_BASH_PATH in the env block of your settings.json. For WSL, open your distribution and run the Linux command inside it; you also start claude there, not from PowerShell.

Updating Claude Code

A native install checks for updates at startup and while it runs, downloads them in the background, and switches to the new version the next time you start it. To update right away, run claude update.

Two release channels exist, set with autoUpdatesChannel or in /config under Auto-update channel:

  1. latest, the default: every release as soon as it ships.
  2. stable: a version that is typically about a week old and skips releases with major regressions.

Homebrew picks the channel by cask name: claude-code follows stable, claude-code@latest follows latest. Upgrade those with brew upgrade, WinGet with winget upgrade Anthropic.ClaudeCode. For npm, rerun the install command with @latest; the docs warn that npm update -g may not move you to the newest release.

To stop background checks, set DISABLE_AUTOUPDATER to "1". That still allows claude update. To block every update path, for example because IT distributes versions itself, use DISABLE_UPDATES.

The misunderstanding: “npm means it runs on Node”

Many guides still lead with npm install -g. According to the setup docs, the npm package now installs the same native binary as the installer, through a per-platform dependency, and the claude command does not call Node at all. npm is just another delivery route. Two related traps: never install with sudo npm, because Claude Code then cannot update itself, and installing the VS Code extension does not put claude on your PATH. The extension bundles its own copy; for the terminal you install the CLI separately.

Rolling it out to a team

IT does not need to touch each developer’s settings. Claude Code reads managed settings, which outrank user, project and local settings:

  1. Server-managed from the claude.ai admin console: fetched at startup and polled hourly.
  2. MDM or OS policy: the com.anthropic.claudecode preferences domain on macOS, or a Settings value under HKLM\SOFTWARE\Policies\ClaudeCode on Windows, through Jamf, Intune or Group Policy.
  3. A file: managed-settings.json in /Library/Application Support/ClaudeCode/ (macOS), /etc/claude-code/ (Linux and WSL) or %ProgramFiles%\ClaudeCode\ (Windows).

Useful keys for a rollout: autoUpdatesChannel to keep everyone on stable, minimumVersion so updates never go below a version, and requiredMinimumVersion and requiredMaximumVersion to refuse to start outside a range. Permission deny rules, such as blocking reads of .env, go in the same file. Verify on one machine with /status: the Setting sources line should name the managed source. Anthropic publishes starter templates for Jamf, Intune and Group Policy in the claude-code repository under examples/mdm. One catch: cloud sessions on Anthropic’s machines do not read a device’s MDM profile or file, so policy for those has to come from server-managed settings.

What an install does not give a team

A managed rollout gives every developer the same binary, version and rules. It does not give them the same knowledge. What Claude Code learns in one developer’s sessions stays on that machine, and a new hire starts from the project CLAUDE.md and nothing more. See how Claude Code memory works and Claude Code memory for teams.

Where Bombos fits

Installing Claude Code is the easy part; making every install know what the team knows is the harder one. Bombos is a plugin that gives Claude Code and the team’s other AI tools one shared memory: team knowledge, rules the team has learned, and what already sits in mail, documents and repos, traceable to the source, in the cloud or on your own server. One developer can add it to their own setup first.

Related questions

Do I need Node.js to install Claude Code?

No. The native installer, Homebrew and WinGet need no Node.js. The npm package asks for Node.js 22 or later, but it installs the same native binary, which does not use Node at runtime.

Do I need admin rights on Windows?

No. The docs say you do not need to run the install command as Administrator. Git for Windows is optional and gives Claude Code Git Bash for its Bash tool.

How do I update Claude Code by hand?

Run claude update. For Homebrew use brew upgrade claude-code, for WinGet winget upgrade Anthropic.ClaudeCode, and for npm npm install -g @anthropic-ai/claude-code@latest.

Can I use Claude Code on the Free plan?

No. Claude Code needs a Pro, Max, Ultra, Team, Enterprise or Console account, or a cloud provider such as Amazon Bedrock, Google Cloud's Agent Platform or Microsoft Foundry.

How do I uninstall it?

For a native install on macOS, Linux or WSL, remove ~/.local/bin/claude and ~/.local/share/claude. Settings and history live in ~/.claude and ~/.claude.json; delete those only if you want them gone too.

Sources

  1. Claude Code docs: Advanced setup
  2. Claude Code docs: Deploy managed settings
  3. Claude Code docs: Overview
  4. Claude Code docs: Use Claude Code in VS Code
The first half hour · free

What does your AI forget?

  1. 01You tell us which AI you use and where it keeps starting over.
  2. 02We show what a shared memory changes there, on your own examples.
  3. 03You keep the plan, with or without Bombos.
Piet Baudoin
Piet BaudoinYou talk to Piet, from the Bombos teamDutch team from Utrecht and Nijmegen · data in Europe
We reply the same working day.