Skip to content
Mia Automation
NLEN Sign in Put Mia to workGet started

How to Update Claude Code, Choose a Channel and Pin a Version

Run claude update to install the newest Claude Code right away. A native install also updates itself in the background; Homebrew, WinGet, npm and Linux packages need their own upgrade command. We tested it on a Windows 10 PC: claude update took version 2.1.300 to 2.1.322 in one step. On the stable channel the same start ended at 2.1.311, and with DISABLE_UPDATES set the command refused.

Claude in practiceUpdated 5 min read

Tested by us on 11 November 2026.

Animated diagram: from Claude Code 2.1.300 a dot travels along three paths in turn; the default latest channel ends at 2.1.322, the stable channel at 2.1.311, and DISABLE_UPDATES keeps 2.1.300

Update by install method

First find out how you installed it. claude doctor prints a Running: line such as native (2.1.322), plus whether auto-updates are on. Then use the matching command.

Commands from Anthropic's setup docs, checked November 11, 2026.
Installed withUpdate commandUpdates on its own?
Native installer (curl, PowerShell, CMD)claude updateYes, in the background; takes effect next start
Homebrewbrew upgrade claude-code or brew upgrade claude-code@latestNo
WinGetwinget upgrade Anthropic.ClaudeCodeNo
npmnpm install -g @anthropic-ai/claude-code@latestYes, if npm can write without sudo
apt / dnf / apksudo apt update && sudo apt upgrade claude-code (or dnf/apk equivalent)No
VS Code extensionUpdate it in the Extensions viewFollows VS Code's extension updates

Skip npm update -g for this. According to the docs it respects the version range from the original install and may not move you to the newest release. On WinGet the upgrade can fail while Claude Code is running, because Windows locks the file; close your sessions first.

Update now with claude update

  1. Check your version

    Run claude --version. Ours said 2.1.300 (Claude Code) because we had installed an older release on purpose.

    bash
    claude --version
  2. Update

    Run claude update. It prints the current version, the channel it checks and the target, then Successfully updated from 2.1.300 to version 2.1.322. You don't need to be signed in.

    bash
    claude update
  3. Restart open sessions

    Running sessions keep the old version until you start them again. Exit and run claude -c to continue where you were.

PowerShell window: an older Claude Code 2.1.300 installed, claude update moving it to 2.1.322, and claude doctor showing the auto-update channel set to stable (opens at full size)

Latest or stable: pick a channel

Claude Code has two release channels. latest, the default, gets every release as soon as it ships. stable serves a version the docs describe as typically about a week old, skipping releases with major regressions. On our test PC that difference was concrete: on the same morning, latest meant 2.1.322 and stable meant 2.1.311.

json
{
  "autoUpdatesChannel": "stable",
  "minimumVersion": "2.1.300"
}

~/.claude/settings.json. You can also switch in /config under Auto-update channel.

minimumVersion is a floor: updates never install anything older. Without it, switching an up-to-date install to stable could move you back. One catch from the docs: a newly launched model can need a newer version than stable serves, so switch back to latest if a model doesn't show up.

Stop updates or stay on one version

SettingWhat it stopsWhat still works
DISABLE_AUTOUPDATER=1Background updatesclaude update and claude install by hand
DISABLE_UPDATES=1Every update pathNothing: claude update refuses

Put either one under env in settings.json. We tested DISABLE_UPDATES: claude update answered Updates are disabled by your administrator. Contact your IT team to get the latest version. That's the message even when you set it yourself, so leave a note for whoever comes after you.

PowerShell window: with DISABLE_UPDATES set, claude update refuses and claude doctor shows updates disabled; after switching to the stable channel, claude update moves 2.1.300 to 2.1.311 (opens at full size)

On machines that run scheduled jobs unattended, we turn off background updates and update on purpose, at a moment we pick. A tool that changes under a job at night makes failures harder to trace. On machines where people work interactively, we stay on latest.

Go back to an older version

The native installer takes a version number. This is how we installed 2.1.300 for the test; it works the same for rolling back after a bad release. Turn off auto-updates afterwards, or the next start pulls you forward again.

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

macOS, Linux and WSL. On Windows PowerShell: & ([scriptblock]::Create((irm https://claude.ai/install.ps1))) 2.1.300

When updating goes wrong

  • Multiple installations found in claude doctor. An old npm install sits next to the native one, and the PATH order decides which runs. Remove the one you don't use. We hit this on a Linux machine.
  • Package managers lag behind. The same day claude update gave 2.1.322, WinGet listed Anthropic.ClaudeCode at 2.1.317. Use the native installer if you want releases on day one.
  • Auto-update failed in the footer. Run claude doctor; it shows the last update attempt and the error. The troubleshooting docs list fixes per cause.

Questions

How do I update Claude Code?

Run claude update for a native install. Homebrew, WinGet, npm and Linux packages use their own upgrade command; see the table at the top.

Does Claude Code update automatically?

Native and npm installs do, in the background, and the new version starts next time. Homebrew, WinGet, apt, dnf and apk don't, unless you set CLAUDE_CODE_PACKAGE_MANAGER_AUTO_UPDATE=1 for Homebrew or WinGet.

How do I check which version I have?

claude --version prints it. claude doctor adds the install method, the channel and the last update attempt.

How do I stop Claude Code from updating?

Set DISABLE_AUTOUPDATER=1 to stop background updates, or DISABLE_UPDATES=1 to block claude update too.

Sources