How to Update Claude Code to the Latest Version

If you're wondering how to update Claude Code to the latest version, the good news is that it's usually painless — Claude Code is designed to keep itself current in the background. But there are times when you want to force an update, confirm exactly which version you're running, or fix an install that's stuck on an old release. This guide walks through every reliable path: the built-in auto-update, the manual npm flow, how to verify your version, and how to make sure you never miss a release in the first place. Claude Drops is an independent project and is not affiliated with Anthropic.

How Claude Code updates itself

Claude Code is Anthropic's agentic coding tool that runs in your terminal and integrates with editors like VS Code and JetBrains IDEs. It's distributed as the npm package @anthropic-ai/claude-code, and for most people the short answer to how to update Claude Code is: you usually don't have to do anything. Claude Code generally checks for new releases and updates itself automatically, so the version you launch tomorrow is often newer than the one you launched today.

Releases ship frequently — sometimes multiple times a week — with bug fixes, performance work, and new capabilities. You can see the full history on the Claude Code changelog, which mirrors the official CHANGELOG.md from the anthropics/claude-code repository.

Check your current Claude Code version

Before you update, it helps to know where you're starting. To check your Claude Code version, ask the CLI directly:

claude --version

This prints the version number Claude Code is currently running. You can also check from inside an interactive session — Claude Code exposes built-in slash commands, including diagnostic ones that surface version and environment details. If you're unsure of the exact command on your build, run /help inside Claude Code to list what's available, since the slash-command surface evolves between releases.

Compare the number you see against the newest entry on the changelog. If they match, you're already on the Claude Code latest version and there's nothing to do. If yours is older, read on.

How to update Claude Code manually

When you want the newest release immediately — instead of waiting for the background updater — the most common path is a global npm install. If you originally installed Claude Code globally via npm, re-running the global install pulls the latest published version:

npm install -g @anthropic-ai/claude-code

That command installs the newest published version over your existing one. Afterward, confirm it took effect:

claude --version

After updating, fully restart Claude Code — quit the running session and start a new one — so the new binary is loaded. If you have Claude Code open in multiple terminals or an IDE extension, restart those too.

If you installed without npm

Anthropic has offered more than one installation method over time, including native installers and package-manager options beyond npm. If npm install -g doesn't match how you set things up, don't guess — the safest move is to follow the official, current instructions in the Claude Code docs, which always reflect the installation and update flow for the latest release.

Troubleshooting a stuck or failed update

If claude --version still shows the old number after updating, work through these in order:

• Restart everything. Quit all Claude Code sessions and IDE extensions, then open a fresh terminal. A new binary won't load into an already-running process.
• Check which binary is on your PATH. Run which claude (macOS/Linux) or where claude (Windows). If two copies are installed from different methods, your shell may be launching the old one.
• Watch for permission (EACCES) errors during a global npm install. These usually mean your npm global directory needs different permissions or a different prefix. Configuring npm so global installs don't require sudo is the long-term fix — npm's own docs cover this.
• Confirm Node.js is recent enough. Claude Code requires a reasonably modern Node.js LTS. An outdated Node can block installs or cause odd runtime errors.
• Reinstall as a last resort. Uninstall with npm uninstall -g @anthropic-ai/claude-code and reinstall fresh if the install is corrupted.

How to know when a new version shipped

Knowing how to update Claude Code is only half the battle — the other half is knowing when there's something worth updating for. Because releases are frequent, it's easy to be several versions behind without realizing a feature you'd love already exists. A few ways to stay current:

1. Read the release notes. Each version on the Claude Code changelog is summarized so you can quickly see new features, fixes, and any breaking changes before you upgrade.
2. Watch the source. The official CHANGELOG.md on GitHub is the canonical record; you can watch the repo for releases.
3. Get push notifications. Claude Drops is an iOS app that sends a push the moment a new Claude Code release lands, so you can decide whether to update right away — no manual polling required. Grab it from the app.

For a deeper look at staying current as a daily Claude Code user, see how to stay up to date with Claude Code, and if you want to get more out of the release notes themselves, our guide to reading the Claude Code changelog breaks down how to scan a release in seconds.

Quick reference

That's the whole update loop: check your version, update (auto or via npm), restart, and confirm. Lean on auto-update for the day-to-day, and reach for the manual npm command when you want the newest release right now. When in doubt about exact syntax for your install method, the official Claude Code docs are the source of truth.

Want to never wonder whether you're on the latest build? Browse the Claude Code changelog to see what's new across recent releases, and get the Claude Drops app so the next release pings your phone the moment it ships. (Claude Drops is an independent project, not affiliated with Anthropic.)