[BUG] Restart to apply stuck, no way to update

Not a fan how these get auto-classified as duplicate without context. But you shouldn't need to re-install. I had a couple problems trying to upgrade 1.0.16 today as well.

Can someone link the duplicate? I did a search before creating the issue and didn't see anything. I'm curious what was said and if there is a solution.

Same thing has happened to me in the past. I searched and could not find anything. Something auto-tags the issues as dupes, not sure how or to what.

Some additional context and how I got it to work:

➜  ~ which claude
/home/brennan/.bun/bin/claude

lrwxrwxrwx 1 brennan brennan  59 Jun  5 15:13 claude -> /home/brennan/node_modules/@anthropic-ai/claude-code/cli.js

npm uninstall -g @anthropic-ai/claude-code
rm -rf ~/node_modules/@anthropic-ai

which claude
claude not found

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

Might have been a stale version of Claude Code, not sure why it was going through bun. But uninstalling the global module and then finding any trace of it that might have been left behind and wiping that and then doing an npm install after that seems to have resolved the issue.

I'm on 1.0.17 now.

No need to re-install, just run 'claude update'

The text ✓ Update installed · Restart to apply should be updated to specify that then. Restarting did nothing but hard to say whether that was because of multiple versions from an early Claude and stale symlinks.

Agreed, it took me a while to figure that out too, the text is misleading. I run 'claude update' (when I gauge that the latest release is stable) at every start up, but currently have downgraded to 1.0.9 until they sort out the latest string of bugs. 1.0.9 is very stable, no issues in terms of crashing

Ran into the same issue of not being able to upgrade on a completely different system and OS (this time MacOS). I tried claude update but it did not work.

Solution was the same, uninstall the npm page. which claude still pointed to a working old version, rm -rf node_modules/@anthropic-ai/claude-code (symlink showed where the npm package was), and then remove the symlink. Then install the npm package again.

I can only guess earlier versions of CC installed differently and the claude update is not aware of how to clean up the old version. Hard to say for sure but hopefully this helps anyone else trying to upgrade or for the devs to be able to clear out the old version.

Claude Code Status v1.0.17

I faced the same issue. Getting message: "Auto-updating to v1.0.24" that turns into "Update installed · Restart to apply" which implies all I need to do is restart.

Running claude update worked.

I am having the same issue (have for the last 5 days or so) trying to update to 1.0.24

Sorry for the trouble here. We are working towards a new way of distributing Claude Code that should be more reliable than npm but it's tricky to get this right and I want to be careful.

In the meantime, most problems should be resolvable by doing
npm install -g @anthropic-ai/claude-code

Sorry for the trouble here. We are working towards a new way of distributing Claude Code that should be more reliable than npm but it's tricky to get this right and I want to be careful. In the meantime, most problems should be resolvable by doing npm install -g @anthropic-ai/claude-code

Even after doing this, I still get the message when I restart Code.

But, like @apostolisCodpal claude update worked

It is not working when I do claude update or npm install -g @anthropic-ai/claude-code. I get a message saying it is updated, but now Claude code wont let me run it because I'm on 1.0.17

you may have an alias or unusual location that is making claude update not work
best thing to do is to npm install -g @anthropic-ai/claude-code and make sure you are running the global version. you can use commands like which claude to figure out what might be going wrong.

Have you tried deleting pre-existing Claude folders before the update? Just backup any important files within those if needed. I had to do similar actions...

Closing this out, please create a new issue if you have issues with the auto-updater

This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.