OmniscioGuidesUpdate Claude Code
Update Claude Code
Claude Code updates with one command, claude update, and a native installation updates itself without you running anything. Which of those two applies depends on how you installed it.
The command is the same one everywhere, and the rest of this page is the difference between a native install and one your package manager owns.
Last checked against Anthropic's setup documentation on November 16, 2026. By the Omniscio team. Updated .
On this page
- Update it now
- Which install do you have?
- The command for each install method
- What a native install does on its own
- Choose the release channel
- Pin a version, or stop updates
- When an update fails
- Several sessions, and shared storage
If the update is what brought you here because it did not finish, the auto-update failed guide covers the message and the documented fix for each method.
Update it now
Open a terminal and run:
claude updateIt is the right first thing to type whatever route you used. On an install a package manager owns, like Homebrew, WinGet or apk, it reports Claude is up to date! instead of updating, and that line does not mean you are up to date.
Otherwise there are two results. When a new version installs, it reports Successfully updated from <old version> to version <new version>.
When you are already current, it reports Claude Code is up to date (<version>). Installs managed by Homebrew, WinGet or apk report Claude is up to date! instead.
To see what the last attempt did, run claude doctor. Anthropic describes it as read-only install and settings diagnostics printed without starting a session.
Sources: the update-manually section of Anthropic's setup page and the claude doctor row in the CLI reference, read November 16, 2026.
Which install do you have?
The command depends on the route you installed with, so find that out first. On macOS and Linux, this lists every copy of claude your terminal can find:
which -a claudeA native install is a symlink at ~/.local/bin/claude pointing into ~/.local/share/claude/versions/. A legacy local install sits in ~/.claude/local/, and a global npm install shows up in npm -g ls @anthropic-ai/claude-code.
On Windows, where.exe claude lists every copy. In PowerShell, Test-Path "$env:USERPROFILE\.local\bin\claude.exe" answers for the native one on its own.
More than one install is a real problem rather than a curiosity. Anthropic warns that multiple installations can cause version mismatches and unexpected behaviour, and recommends keeping the native one and removing the rest. The uninstall guide has the removal command for each.
Source: the Check for conflicting installations section of Anthropic's install troubleshooting page, read November 16, 2026.
The command for each install method
Anthropic's rule is simple: Claude Code's own updater manages native and npm installs, and your package manager manages everything else.
| Installed with | Update with | Automatic by default |
|---|---|---|
| Native installer | claude update | Yes |
| npm | npm install -g @anthropic-ai/claude-code@latest | Yes, unless the npm global folder is not writable |
| Homebrew, stable cask | brew upgrade claude-code | No |
| Homebrew, latest cask | brew upgrade claude-code@latest | No |
| WinGet | winget upgrade Anthropic.ClaudeCode | No |
| apt | sudo apt update && sudo apt upgrade claude-code | No |
| dnf | sudo dnf upgrade claude-code | No |
| apk | apk update && apk upgrade claude-code | No |
Homebrew and WinGet can opt in to background upgrading. Anthropic says setting CLAUDE_CODE_PACKAGE_MANAGER_AUTO_UPDATE to 1 makes Claude Code run the upgrade itself when a new version is available, then show a restart prompt.
That upgrade touches only the Claude Code package, not your other software. apt, dnf and apk still need you, because those commands want elevated privileges.
On npm, Claude Code updates itself; the command in the table is how you force it now. Use that rather than npm update -g, which respects the version range from the original install and can leave you behind.
Sources: the auto-updates and update-manually sections of Anthropic's setup page, including its Homebrew, WinGet, npm and Linux-package-manager notes, read November 16, 2026.
What a native install does on its own
Anthropic describes a background check at two moments: when Claude Code starts, and periodically while it runs. An update found there downloads and installs in the background.
The version you are running does not change under you. The new one takes effect the next time you start Claude Code, which is why a session in progress is never switched mid-answer.
claude doctor reports the result of the most recent attempt. If that attempt failed, the footer message in a session says so, and the auto-update failed guide covers it.
One npm case is worth knowing. If the npm global folder is not writable, Anthropic says Claude Code shows a one-time notice at startup and claude doctor lists the fixes.
A custom launcher changes the picture. If you replaced ~/.local/bin/claude with your own script or symlink, updates leave it in place and Claude Code keeps every installed version on disk. To hand control back, Anthropic's step is to remove that file and run claude update.
Source: the auto-updates section of Anthropic's setup page, read November 16, 2026.
Choose the release channel
The autoUpdatesChannel setting decides which releases auto-update and claude update reach for. "latest" is the default and delivers new features as soon as they ship.
"stable" serves a version that Anthropic says is typically about one week old, skipping releases with major regressions. Set it inside a Claude Code session by typing /config and choosing Auto-update channel, or in your settings file:
{
"autoUpdatesChannel": "stable"
}Anthropic notes one consequence. A native install set to stable updates to the stable version even when that version is older than yours, so switching can move you backwards.
A newly launched model can need a newer Claude Code than the stable channel serves. Moving to the latest channel is Anthropic's answer for running that model now.
Homebrew picks a channel by cask name instead, and the apt, dnf and apk repositories pick one by repository URL. The Mac and Linux install guides name both in each route.
Source: the Configure release channel section of Anthropic's setup page, read November 16, 2026.
Pin a version, or stop updates
A few settings control it. minimumVersion sets a floor: background updates and claude update refuse to install anything below it. That is how you move to stable without going backwards.
{
"autoUpdatesChannel": "stable",
"minimumVersion": "the version claude --version printed"
}In /config, switching to stable and choosing Stay on current version fills that number in for you, from the version you are running. Outside it, claude --version prints that number. Anthropic says switching back to latest in /config clears the minimum.
To stop the background check, add DISABLE_AUTOUPDATER to the env key of your settings.json, which sits in ~/.claude/:
{
"env": {
"DISABLE_AUTOUPDATER": "1"
}
}Anthropic notes this leaves claude update and claude install working. On a native or npm install, claude doctor then shows Auto-updates as disabled (set by env: DISABLE_AUTOUPDATER).
DISABLE_UPDATES is the harder switch. It blocks every update path, including manual ones, and Anthropic intends it for teams that distribute Claude Code through their own channels.
Organizations have two more managed settings. requiredMinimumVersion and requiredMaximumVersion make Claude Code refuse to start outside that range, and updates respect the maximum.
To install one particular version of the native binary instead, claude install takes a version number, or the channel names stable and latest — for example claude install stable.
Sources: the Pin a minimum version, Disable auto-updates and Set version limits sections of Anthropic's setup page, and the claude install row in the CLI reference, read November 16, 2026.
When an update fails
A failed update is not a broken install. Claude Code keeps working on the version you already have, and the auto-update failed guide covers the footer message and the documented remedy for each method.
Two failures look like something else entirely. On Windows an update that leaves no claude.exe behind turns into 'claude' is not recognized, which Claude Code on Windows explains.
On any system, a terminal that says command not found: claude after an update is usually a PATH or a missing file rather than the update itself. The command not found guide separates the two.
Package managers have their own timing. Anthropic lists a known issue where Claude Code notifies you of an update before the new version reaches Homebrew, WinGet or a Linux repository, and its advice is to wait and try again.
Sources: the auto-updates and known-issue notes on Anthropic's setup page and the install troubleshooting page, read November 16, 2026.
Several sessions, and shared storage
A background update is easy to miss when several sessions are open. Anthropic documents one case where that matters a great deal: on shared network storage, an in-place upgrade can remove the binary a session on another machine is still running.
Its advice for that setup is to keep each version in its own directory, delete an old one only when no machine can still be running it, and set DISABLE_UPDATES so only your own tooling installs new versions.
DISABLE_AUTOUPDATER alone is not enough there, because people can still run claude update and claude install by hand.
Omniscio, the desktop app we make for running many Claude Code sessions at once, has a one-click Update in Settings under Connected Tools. The toolchain update page says it runs claude update against the binary your sessions actually use, or winget upgrade where WinGet installed it.
Omniscio is free with up to 8 projects, and Pro is $20/month or $192/year; neither plan includes an AI allowance.
Sources: the Install on network storage section of Anthropic's setup page, read November 16, 2026, and our toolchain update page, read the same day.
Where these answers come from
- Anthropic, Advanced setup: the auto-update behaviour, the manual command and its messages, release channels,
minimumVersion, the managed version limits,DISABLE_AUTOUPDATER,DISABLE_UPDATES, the npm and package-manager upgrade commands, and the network-storage warning. Read November 16, 2026. - Anthropic, CLI reference:
claude update,claude install [version]andclaude doctor. Read November 16, 2026. - Anthropic, Troubleshoot installation and login: the conflicting-installations check on macOS, Linux and Windows. Read November 16, 2026.
- Anthropic, environment variables:
CLAUDE_CODE_PACKAGE_MANAGER_AUTO_UPDATE,DISABLE_AUTOUPDATERandDISABLE_UPDATES. Read November 16, 2026.
The release checked here was 2.1.325, the version npm served and claude --version printed on November 16, 2026. Anthropic's install troubleshooting page keeps version markers such as "Before v2.1.281", so read the page again before trusting an old copy of this one.
Common questions
How do I update Claude Code?
Run claude update in your shell. On a native install it reports Successfully updated from the old version to the new one, or Claude Code is up to date with the version you already have. Homebrew, WinGet, apt, dnf and apk installs use their own upgrade command instead. An npm install updates itself, the same as a native one.
Does Claude Code update itself?
A native installation does. Anthropic says it checks for updates on startup and periodically while running, downloads and installs them in the background, and switches to the new version the next time you start Claude Code. Run claude doctor to see the result of the last attempt it recorded.
What is the difference between the latest and stable channels?
Latest is the default and gives you new features as soon as they are released. Stable serves a version that is typically about one week old and skips releases with major regressions. Set it with autoUpdatesChannel in settings.json, or through the Auto-update channel entry in /config.
Will switching to stable downgrade my install?
It can. Anthropic says a native installation on stable updates to the stable version even when that version is older than yours. To avoid the downgrade, set minimumVersion to the version you are running; background auto-updates and claude update then refuse to install anything below it.
How do I stop Claude Code updating itself?
Set DISABLE_AUTOUPDATER to 1 in the env section of your settings.json. That stops the background check, and Anthropic says claude update and claude install still work. To block every update path, including manual ones, set DISABLE_UPDATES instead.
Why does a WinGet upgrade fail while Claude Code is open?
The WinGet upgrade can fail while Claude Code is running because Windows locks the executable. Anthropic says Claude Code then shows you the manual command instead of doing it for you. Close every Claude Code session, then run winget upgrade Anthropic.ClaudeCode.
Update once, from the screen your sessions already run in
Omniscio runs many Claude Code sessions side by side and updates the binary they actually use from one screen. The features page lists what it does today.