How to Update Claude Code (and Check Your Version)
How to update Claude Code: run claude update, or let the native install update itself. Check your version with claude --version. npm and Homebrew differ.
How do you update Claude Code? Run claude update in your terminal. If you installed it with Anthropic’s native installer, you may not need to: it updates itself in the background.
That second part surprises people. Before you type anything, answer a few questions, and they’ll tell you exactly what to do.
First question: how did you install it?
This decides everything. Here are the four common ways to install Claude Code, and they don’t all update the same way.
| How you installed | Updates itself? | Command to update now |
|---|---|---|
| Native installer (curl or PowerShell) | Yes | claude update |
| npm | Only if npm’s global folder is writable | npm install -g @anthropic-ai/claude-code@latest |
| Homebrew | No, by default | brew upgrade claude-code |
| WinGet | No, by default | winget upgrade Anthropic.ClaudeCode |
If you used the Homebrew cask called claude-code@latest, upgrade that name instead. On Linux, apt, dnf and apk installs update with your normal system upgrades.
Don’t know which one you used? The next question finds out.
Do you have more than one copy?
Run this on Mac or Linux:
which -a claude
On Windows, run where.exe claude.
One result is good. Two results means two installs, and Anthropic says that causes version mismatches. You update one copy, and your terminal keeps running the other.
If you find two, keep the native one and remove the extra. For an npm copy, that’s npm uninstall -g @anthropic-ai/claude-code.
Which version are you on right now?
Ask Claude Code directly:
claude --version
The short form is claude -v. It prints something like 2.1.211 (Claude Code).
Already inside a session? Type /status. It shows your version, model and account. Type /release-notes to see what changed in each version.
If it updates itself, why are you still on an old version?
Because updates land on the next start. Claude Code checks for updates when it starts and while it runs, and downloads them in the background. They take effect the next time you open it.
So if you’ve had one session open for days, you’re running the version you started with. Close it and open a new one.
Want it now? Run claude update. It either reports Successfully updated from one version to another, or tells you Claude Code is up to date.
What if the footer says “Auto-update failed”?
You can keep working without doing anything. Only the background update failed to install.
To see why, run claude update in your shell. If that fails too, it prints the real error. claude doctor also shows the date of the last update attempt, but not the cause.
Do you want every update the day it ships?
Claude Code follows one of two release channels, and you choose which one:
- latest is the default. You get new features as soon as they ship.
- stable runs about a week behind and skips releases with major problems.
Switch in a session with /config, then Auto-update channel. Or set "autoUpdatesChannel": "stable" in your settings.json.
If you pick stable while you’re already ahead of it, Claude Code asks whether to stay on your current version or step back.
Should you ever turn updates off?
Rarely. To stop the background check, set DISABLE_AUTOUPDATER to "1" in the env section of your settings.json. claude update still works when you want it.
Don’t do this on your main machine just because updates feel noisy. Updates carry security fixes, and Homebrew and WinGet users already have to remember to run them.
So what do you actually need to do?
Now look back at your answers to those questions.
Native install, one copy? Restart Claude Code now and then, and run claude update when you want the newest version today. That’s it.
Homebrew, WinGet or npm? Put the update command from the table somewhere you’ll see it, and run it every week or two. Or switch to the native installer and stop thinking about it. If npm is giving you trouble, see Fixing Claude Code npm Install Errors.
Frequently asked questions
Does Claude Code update automatically? Yes, if you used the native installer. It downloads updates in the background and applies them the next time you start it. Homebrew and WinGet installs don’t update themselves by default.
How do I check my Claude Code version?
Run claude --version or claude -v in your terminal. Inside a session, type /status to see the version along with your model and account.
Why shouldn’t I use npm update to update Claude Code?
Anthropic says npm update -g respects the version range from your original install and may not move you to the newest release. Use npm install -g @anthropic-ai/claude-code@latest instead.
Does updating Claude Code cost anything? No. Updates are free. You pay for the plan, starting with Pro at $20 a month. See How Much Does Claude Code Cost?
New to Claude Code? Start with What Is Claude Code?, or watch my free video, where I build a real site with it start to finish. Watch the free video.