How to Check and Update Your Claude Code Version

Claude Code shipped six releases between June 17 and June 26, 2026, moving from version 2.1.181 to 2.1.195 according to its official changelog. That works out to roughly one release every 36 hours. Each patch carries bug fixes, new environment variables, and behavioral changes that affect how the CLI handles your codebase.

The tool uses semantic versioning in a major.minor.patch format. As of late June 2026, all releases sit on the 2.1.x line, meaning the core interface stays stable while patches ship continuously. A jump from 2.1.181 to 2.1.195 in under two weeks is the normal pace, not an anomaly.

To put the release velocity in context: a developer running 2.1.181 on June 17 would miss a 37% reduction in CPU usage during streaming (landed in 2.1.191), the /rewind command for resuming conversations after /clear (also 2.1.191), and a fix for background agents that kept running after being stopped. On teams where multiple people run Claude Code against the same project, version drift can produce inconsistent behavior from identical prompts.

Claude Code now powers a measurable share of active development. The tool authored approximately 4% of all public GitHub commits as of February 2026, according to data compiled by SerpSculpt from Anthropic's reporting. At that scale, version management is not a niche concern.

The fast check:

claude --version

This prints the installed version number (for example, 2.1.195) and exits. It works across all installation methods: native installer, Homebrew, npm, WinGet, and Linux package managers.

For a deeper diagnostic, run:

claude doctor

claude doctor reports more than the version number. It checks your installation health, shows the result of the most recent auto-update attempt, identifies permission issues that might block future updates, and flags configuration problems. When an update silently fails, this is the first command to run.

What to look for in the output:

• Your installed Claude Code version
• Whether the last background update check succeeded or failed
• Network or permission issues that block updates
• Your active release channel (stable or latest)
• Conflicting installations, like having both an npm and native install on the same machine

If claude --version returns command not found, Claude Code is not on your PATH. The most common cause is that you ran the native installer but have not restarted your terminal, so the updated shell profile has not loaded yet. Open a new terminal window and try again.

How you update depends on how you installed. Here is the right command for each method.

Native Installer (Recommended)

Native installations auto-update in the background. Claude Code checks for new versions on startup and periodically while running. Updates download silently and take effect the next time you launch the CLI.

To force an immediate update:

claude update

Homebrew

Homebrew installations do not auto-update by default. Upgrade manually with:

brew upgrade claude-code

If you installed the latest-channel cask, use brew upgrade claude-code@latest instead.

To enable automatic upgrades through Homebrew, add this to your settings:

{
  "env": {
    "CLAUDE_CODE_PACKAGE_MANAGER_AUTO_UPDATE": "1"
  }
}

Claude Code will then run the Homebrew upgrade command when a new version is available and prompt you to restart.

npm

Update with:

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

Do not use npm update -g. It respects the semver range from your original install and may not actually move you to the newest version. Also avoid sudo npm install -g, which creates permission problems.

WinGet (Windows)

winget upgrade Anthropic.ClaudeCode

Close Claude Code before running this. Windows locks the executable while it runs, and the upgrade will fail if the process is active.

Linux Package Managers

For apt (Debian, Ubuntu):

sudo apt update && sudo apt upgrade claude-code

For dnf (Fedora, RHEL):

sudo dnf upgrade claude-code

For apk (Alpine):

apk update && apk upgrade claude-code

Package manager installations require manual updates because the upgrade commands need elevated privileges. Claude Code cannot auto-update through these channels.

Installing a Specific Version

If you need an exact version rather than the latest, the native installer accepts a version argument:

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

On Windows PowerShell:

& ([scriptblock]::Create((irm https://claude.ai/install.ps1))) 2.1.189

Via npm:

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

Claude Code offers two release channels that control which versions reach your machine through auto-updates and claude update.

Latest is the default. Every release ships to you as soon as it is published. You get the newest features within hours, but you also absorb any regressions before the team catches them.

Stable serves a version that is typically about one week behind latest. Anthropic holds back releases that introduce major regressions, so stable works as a curated feed. If a release breaks something important, it never reaches stable-channel users.

To switch channels, open Claude Code and run /config, then select Auto-update channel. Or add the setting directly to your settings.json:

{
  "autoUpdatesChannel": "stable"
}

Homebrew users choose a channel by cask name instead of this setting. The claude-code cask tracks stable. The claude-code@latest cask tracks latest.

When to use each channel

Individual developers who want immediate access to new capabilities should stay on latest. The trade-off is occasional rough edges in the first hours after a release.

Teams where behavioral consistency matters benefit from stable. When three developers work on the same project, you want claude to behave the same way for all of them. The one-week buffer filters out regressions while keeping the delay short enough that security and performance fixes arrive quickly.

When switching from latest to stable, Claude Code asks whether to stay on your current version or allow the downgrade. Choosing to stay sets a minimumVersion floor automatically, preventing stable from pulling you backwards to an older build.

Keep your Claude Code output versioned and searchable

Fast.io workspaces give your team a shared home for everything Claude Code produces. Files are automatically indexed for semantic search, and the MCP server lets agents read and write directly. Start with a 14-day free trial.

Start 14-Day Trial

For organizations running Claude Code across multiple developers, version consistency becomes an operational requirement. Two mechanisms handle this: the minimumVersion setting and managed settings.

Setting a Version Floor The minimumVersion setting prevents both auto-updates and claude update from installing anything below a specified version:

{
  "autoUpdatesChannel": "stable",
  "minimumVersion": "2.1.180"
}

This is particularly useful when switching channels. If you are on 2.1.195 via the latest channel and switch to stable (which might currently serve 2.1.181), the minimum version pin keeps you at 2.1.195 until stable catches up.

Managed Settings for Organizations

Enterprise and team deployments can enforce version constraints across every developer through managed settings. These override user and project settings, so individual developers cannot bypass the organization's version policy.

Two additional settings go beyond minimumVersion:

• requiredMinimumVersion makes Claude Code refuse to start if the installed version falls below this value
• requiredMaximumVersion caps updates at a specific version and prevents Claude Code from running above it

Together, these create a version window. An IT team could set requiredMinimumVersion to 2.1.180 and requiredMaximumVersion to 2.1.195, ensuring every developer runs within a tested range.

Disabling Auto-Updates

To stop background update checks entirely, set DISABLE_AUTOUPDATER to 1:

{
  "env": {
    "DISABLE_AUTOUPDATER": "1"
  }
}

This only stops the background check. claude update and claude install still work. To block all update paths, set DISABLE_UPDATES instead. This is designed for organizations that distribute Claude Code through their own deployment pipeline and need users locked to a managed build.

Version consistency matters most when multiple developers or agents interact with the same project. In environments where Claude Code agents produce files stored in shared workspaces, like Fast.io where agents and humans collaborate on the same files through the UI or MCP server, different Claude Code versions may handle tool calls or file operations differently. Pinning a version across the team ensures that workflows tested on one machine behave the same everywhere.

Claude Code publishes its changelog in four places:

• Official docs changelog: The most readable format, organized by version with grouped additions, fixes, and improvements
• GitHub releases: Useful if you already watch the repo or want release notifications
• CHANGELOG.md on GitHub: The raw markdown file, good for diffing between versions
• npm package page: Shows the latest published version number

The official docs format groups changes into three categories: additions, fixes, and improvements. Each version entry includes a date and concise descriptions. Recent entries follow a consistent pattern. Most releases add one or two features (new environment variables, CLI commands, or settings) alongside three to five bug fixes.

What to watch when planning an upgrade

• New environment variables that change default behavior, like CLAUDE_CODE_DISABLE_MOUSE_CLICKS in 2.1.195
• Settings that affect how Claude Code classifies commands, like autoMode.classifyAllShell in 2.1.193
• Performance improvements worth targeting, like the 37% CPU reduction during streaming in 2.1.191
• Fixes for bugs you have been working around

The changelog does not offer a built-in RSS feed, but GitHub's releases page supports Atom at https://github.com/anthropics/claude-code/releases.atom. Subscribe to get notified when new versions ship rather than checking manually.

For teams, reviewing the changelog before moving the minimumVersion or requiredMaximumVersion forward gives you a chance to test new behavior before rolling it out organization-wide.