Claude Update Installed Restart to Update? What to Do
If you searched for “claude update installed restart to update,” you have probably seen this message in Claude Code. When it appears, the current command session may still be using the earlier version. The next step depends on how Claude Code was installed.
- Native installation: close the current terminal, open a new one, and run claude –version.
- Homebrew installation: identify the installed cask, run the matching brew upgrade command, then open a new terminal and verify the version.
Do not restart the entire computer or repeat an installer before checking the installation method. For platform requirements and installation instructions, see the official Claude Code setup documentation.
Claude Update Installed Restart to Update: What It Means
The message indicates that an update has been installed, but the currently running command session may still be using the earlier installation. Closing the terminal and opening a new one gives the shell a fresh environment for resolving the updated command.
A terminal restart means closing the current command window and opening another one. It does not mean restarting macOS, Windows, Ubuntu, Debian, Alpine Linux, or the entire computer. After opening the new terminal, the expected next step is version verification.
First Fix: Open a New Terminal and Check the Version
Close the active Claude Code session and terminal window. Open a new terminal and run:
claude –version
A working installation prints a version number. If the shell says claude is not found or is not recognized, the installation directory may not yet be on PATH. That means the active shell cannot resolve the command; it does not by itself prove that the installation failed.
On Windows, distinguish PowerShell from CMD. The setup documentation provides shell-specific Windows installation instructions, so use the instructions for the shell currently open.
Identify How Claude Code Was Installed
The correct update action depends on the installation method. Identify whether the command came from the native Claude Code installation, Homebrew, WinGet, npm, or a Linux package manager.
- Did you use the native Claude Code installation command?
- Did you install it with Homebrew?
- Did you use WinGet on Windows?
- Did you install it with npm?
- Did a Linux package manager or setup process install it?
These methods can place files in different locations and can have different update behavior. This article gives the documented native and Homebrew actions. It does not provide universal update commands for WinGet, npm, or Linux package managers because the correct command depends on the package and installation method. Use the relevant package documentation for those installations.
Claude Code supports macOS 13.0 or later, Windows 10 version 1809 or later or Windows Server 2019 or later, Ubuntu 20.04 or later, Debian 10 or later, and Alpine Linux 3.19 or later. Claude Code requires an internet connection.
Which Fix Applies to You: A Quick Decision Path
Work from the symptom you can see, and stop as soon as the version looks right.
- You used the native installation: open a new terminal and run claude –version. No separate upgrade command is needed, because this method updates in the background.
- You used Homebrew: a new terminal alone will not change the version. Run the upgrade command that matches your cask, then open a new terminal.
- You used WinGet, npm or a Linux package manager: follow the update guidance for that package, then open a new terminal and check the version.
- You cannot tell how it was installed: run claude doctor. It reports the installed version and any conflicting installations, which gives you a starting point before you change anything.
When you read the version number, compare it with what you expect from your release channel. A stable Homebrew install can reasonably sit behind the latest channel, so a lower number there is not automatically a fault.
Native Installation vs Homebrew: Update Behavior Compared
| Installation method | Documented update behavior | Required user action | Verification command |
|---|---|---|---|
| Native installation | Automatically updates in the background | Open a new terminal and check the version | claude –version |
| Homebrew stable cask | Does not auto-update | Run brew upgrade claude-code, then open a new terminal | claude –version |
| Homebrew latest-channel cask | Does not auto-update | Run brew upgrade claude-code@latest, then open a new terminal | claude –version |
Homebrew offers the stable claude-code cask and the latest-channel claude-code@latest cask. The stable channel is typically about a week behind and skips releases with major regressions.
To identify the installed Homebrew cask, run:
brew list –cask
Look for the exact entry claude-code or claude-code@latest, then use the matching upgrade command. brew list –cask only identifies what is installed; it does not update anything. Do not run both commands as a general troubleshooting step. Opening a new terminal alone does not upgrade a Homebrew cask.
Fixes for PATH, Shell, and Terminal Problems
A terminal that was open during installation or updating may not have the latest environment variables or command paths. Opening a fresh shell can make a newly available installation directory visible to the command resolver.
If a new terminal still reports “command not found” or “not recognized,” check PATH and the installation instructions for the active shell before reinstalling. On Windows, PowerShell and CMD have different command contexts, so a shell-specific error should be investigated in the shell where it occurred.
WSL and native Windows are separate installation contexts. An installation inside WSL is not automatically the same installation as one made in native Windows. Run claude –version in the environment where you intend to use Claude Code.
On macOS and Linux, distinguish a native installation from Homebrew. On Windows, distinguish native Windows from WSL and determine whether WinGet, npm, or another method was used.
When the Version Still Has Not Changed
If the version remains unexpected after the installation-specific update action and a fresh terminal, run:
claude doctor
Claude doctor reports the installed version, the result of the most recent background-update attempt, permission issues, configuration problems, the active release channel, and conflicting installations.
Review the last background-update result for an unsuccessful update. Check permission issues and network problems, then confirm the active release channel. Conflicting installations can also make the active version ambiguous; for example, native and npm installations can both provide a command named claude, while the shell runs only one of them.
For additional version and update diagnostics, see the Claude Code version and changelog guidance. Avoid deleting files until you know which installation is active and which method owns it.
A Safe Verification Checklist for Individual and Team Users
- Open a new terminal after the installation-specific update action.
- Run claude –version and confirm the active version.
- Confirm whether the installation is native, Homebrew, WinGet, npm, or managed by a Linux package manager.
- If Homebrew is involved, identify claude-code or claude-code@latest with brew list –cask.
- Confirm the active release channel before changing update settings.
- Run claude doctor if the version remains unexpected.
- Check for conflicting installations before changing PATH or removing files.
For a project team, agree on one installation method and release channel before standardizing Claude Code versions. This gives developers the same update path and makes version differences easier to investigate.
If the command remains unavailable or the diagnostic output shows an installation error, use the operating-system and installation-method guidance in the official setup documentation.
Next Steps
For official guidance, see the Claude Code troubleshooting documentation and the Claude Code changelog. If another desktop AI app is misbehaving, our guide to ChatGPT Classic not working on Windows covers a similar kind of problem, and our AI tools list for 2026 gives a wider view of the category.
Start with a new terminal and claude –version, then try only the fix that matches your installation method. Changing one thing at a time makes it much easier to see which step actually solved the problem.
Frequently asked questions
Do I need to restart my computer when Claude Code says “update installed, restart to update”?
Usually, no. The documented first action is to open a new terminal window rather than restart the entire computer.
How do I update Claude Code if I installed it with Homebrew?
Run <strong>brew list –cask</strong>. Use <strong>brew upgrade claude-code</strong> for the stable cask or <strong>brew upgrade claude-code@latest</strong> for the latest-channel cask.
Why is Claude Code not found after an update?
The installation directory may not be on PATH, or the command may be running in a different shell or environment. Check the active shell, distinguish WSL from native Windows, and review the installation method.
What should I do if the version still has not changed?
Run <strong>claude doctor</strong> to review the installed version, background-update result, permissions, configuration, release channel, and conflicting installations.
Last updated: 05 November 2026
