Restart?

Status Fixed / completed
Maintainer reply ✓ Yes — bcherny
Activity 13 comments · opened Feb 26, 2025 · closed Feb 26, 2025
💡 Likely answer: A maintainer (bcherny, collaborator) responded on this thread — see the highlighted reply below.

!Image

Hello team,

please tell me how to restart?

View original on GitHub ↗

13 Comments

suradreamz · 1 year ago

!Image

& this issue everyting when it's trying to read an image

gerrywastaken · 1 year ago

By restart, they just mean Close the Claude command and reopen it. This does not mean you need to restart your machine, just Claude.

Under the hood they are just rerunning the npm install command again.

More details here: https://github.com/anthropics/claude-code/issues/141#issuecomment-2685512923

bcherny collaborator · 1 year ago

Yep! Just type exit or quit, or press ctrl+c or ctrl+d twice.

gerrywastaken · 1 year ago

@bcherny the message here is quite unclear as to what needs to be restarted, so perhaps that is the fix here?

mraesener-aubex · 1 year ago

especially you come here if the message sticks after a couple restarts of the cli ;)

mrlfarano · 1 year ago

not only that, I've tried restarting the session, restarting WSL and the message still shows

bcherny collaborator · 1 year ago

Working on improving reliability for this!

mraesener-aubex · 1 year ago

@bcherny any workarounds? I've tried npm update -g @anthropic-ai/claude-code without success - and for the record, rebooting MacOS also didn't help 😅

bcherny collaborator · 1 year ago

Try uninstalling then re-installing

gerrywastaken · 1 year ago

@mraesener-aubex maybe you initially installed with pnpm or something else? If that is the case you will need to rerun the the pnpm install or whatever command you used when originally installing.

Otherwise you may be updating things in npm but then running the old one that was installed via pnpm. That was the case when I had this problem.

mraesener-aubex · 1 year ago

@gerrywastaken thx for the hint - indeed somehow the claude binary was in homebrew's folder even though brew list didn't show it ... and I could install things with npm install -g but the bin folder wasn't in my PATH

long story short: it's working now and the root cause is fixed

gerrywastaken · 1 year ago

Awesome, glad you got it sorted 👍

github-actions[bot] · 1 year ago

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.