How to Update Claude Code and Verify the Version

Update Claude Code through its existing installation channel. Verify the version and executable path, then diagnose why an update may not take effect.

To update Claude Code safely, first identify how the executable you use was installed. Updating a different copy—or changing installation methods without noticing—can leave the old version active even when an upgrade command succeeds.

This guide follows the official setup documentation, checked October 10, 2026. It does not install or update anything on your machine, and it does not assume one fixed version is the newest for every release channel.

Record the version and installation path

Start with read-only checks:

sh
claude --versionclaude doctor

On macOS or Linux, use command -v claude to identify the executable found by your shell. Save the relevant result without exposing private environment values. On a managed computer, ask the owner which installation channel is approved before changing it.

The path matters. An old global package, a native installation, and a package-manager copy can coexist. Your terminal runs the first applicable executable on its search path, not necessarily the one you most recently updated.

Use the existing installation channel

For a native installation, follow the documented updater:

sh
claude update

For Homebrew, upgrade the cask you actually installed. The current documentation distinguishes the stable cask from the latest-channel cask:

sh
brew upgrade claude-code# Or, only if this is the cask you installed:brew upgrade claude-code@latest

For an existing WinGet installation:

powershell
winget upgrade Anthropic.ClaudeCode

Do not run every command in sequence. Choose the matching row. Other package managers have their own procedures in the official setup guide. Review any new permission or agreement rather than approving it merely because this is an update.

What to verify for the 2.1.296 fixes

The official 2.1.296 release, published October 9 and checked October 12, includes fixes worth checking against your workflow. It is a release reference, not an instruction to leave your organization's approved channel.

If this affects youWhat the release fixesWhat to verify after updating
A saved gateway login stopped working after 2.1.295A regression affecting managed gateway sign-in without a configured gateway URLRestart the approved client and check that the intended gateway identity works; do not replace it with a personal key
Headless tasks use MCP servers enabled or disabled per folderSome disabled folder servers could start after a directory change or plugin reloadIn a non-sensitive test project, repeat the relevant transition and confirm disabled integrations remain disabled
You share transcripts or diagnostic logsSome secret values were missed by automatic redactionInspect the material before sharing, even after updating; use only dummy credentials in any redaction test

A client update does not retract logs already shared. If a real credential may have been exposed, use the provider's revocation or rotation process and review where the material was sent.

The same release corrects displayed Sonnet 5.5 cache-read cost calculations. That is a client accounting correction, not evidence that your provider newly discounted your account or refunded previous charges. Compare actual usage against the provider's bill.

These are checks based on the official release notes, not results from testing your installation. Keep any failed check, the actual version, and the relevant redacted error together when reporting a problem.

What changed in 2.1.299

The official 2.1.299 release was published October 14, 2026. Check the changes relevant to your setup after updating through its approved channel.

Your workflowRelevant changeWhat to check
A cloud session rejects an expired claude.ai loginThe refusal now gives a clearer sign-in instructionCheck the account and credential source before following the instruction; the update does not renew the login itself
A third-party gateway uses a custom API base URLSeveral Anthropic-directed auxiliary requests no longer carry the gateway's API keyReview which provider is configured; do not infer that every integration or earlier shared record is now safe
A gateway stream is silent, or Remote Control loses the computerSilent custom-endpoint streams can wait 300 seconds instead of 180; unreachable Remote Control sessions keep text in the input and disable SendDistinguish a longer wait from successful execution; confirm reconnection before treating a message as delivered

None of these changes guarantees that a provider will accept a request or that a stopped computer will resume a task. Record the actual error, selected account, and whether the message reached a running session. A hosted Macshop environment may use a different managed version; do not assume this release is already installed there.

Restart and verify what actually runs

Preserve any unfinished task, close the relevant client when required, and start a fresh session. Run the version and path checks again.

Then test one harmless operation in a familiar project: ask for a description of a file, or run an existing read-only check. A version string confirms the executable; it does not confirm that your model, hooks, or integrations still behave as expected.

For workflows that use model-change hooks, consult the model-switch hook guide and check the relevant behavior separately. Do not use a successful update as proof that every project configuration is compatible.

If the version did not change

Check these explanations before reinstalling:

  • Your release channel intentionally trails another channel.
  • The package manager has not published the desired release yet.
  • A different executable is earlier on the shell's search path.
  • A long-running client has not restarted.
  • Organization policy controls the version.

Keep the exact error and the installer identity. Do not respond to a permission problem by broadly changing filesystem ownership, deleting configuration folders, or adding administrator privileges to an unrelated command.

Keep team updates deliberate

A team should record the tested version, installation channel, and affected integrations. Test an upgrade on one representative project before making it the baseline for everyone. If a feature needs a newer version, link to that feature's requirement rather than turning the article title into a permanently stale “latest version” number.

An update also does not grant a new model or subscription entitlement. The usage-limit guide addresses capacity failures that an installer cannot fix.

If you use a managed Macshop route, follow that route's supported environment rather than running host-level upgrade commands you do not own. The Claude Code on Macshop guide explains how to evaluate the product path; start a workspace only after checking that it supports your intended workflow.