You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[BUG] Hanging / Freezing in the middle of work - CPU sample attached #1554
Claude CLI version: claude 1.0.10, node version v23.11.0
Operating System: macOS 15.5
Terminal: iTerm2
Feedback ID: a80a33ea-5a52-4894-90d0-e36f4aca41fc
Bug Description
Claude code has started hanging and freezing in the middle of its work. It remains hung indefinitely. The only way to get out of this hang is to quit and relaunch the terminal but then the work is lost. Started happening after 1.0.9 I believe.
Steps to Reproduce
Any prompt
Starts working normally
After a few steps it hangs on whatever it's doing - no animation, cannot type anything, cannot hit escape - nothing.
I can see in Activity Monitor node is hung, here's a CPU sample attached.
I'm using Claude Code inside of Cursor / VS Code and it seems to be a bit more reliable. I rarely get long freezes - it does freeze for maybe 30 seconds but always comes back to life. Node CPU usage does spike occasionally but not to very high levels.
This issue has been inactive for 30 days. If the issue is still occurring, please comment to let us know. Otherwise, this issue will be automatically closed in 30 days for housekeeping purposes.
This issue has been inactive for 30 days. If the issue is still occurring, please comment to let us know. Otherwise, this issue will be automatically closed in 30 days for housekeeping purposes.
This issue is still occurring in v2.1.6
Reacted by David White, Rikard and Dmitrii Topornin
Activity
guidedways commentedon Jun 4, 2025
Another CPU sample, freezing constantly.
sample2.txt
sepsi77 commentedon Jun 4, 2025
Happens to me also constantly since 1.0.10, though it does "unfreeze" itself after quite a long wait.
guidedways commentedon Jun 4, 2025
True, I let it run this time for 15 minutes and it came back to life, only to hang again. I can see the CPU spike in Activity Monitor too.
I've just upgraded node to
v24, killed all instances ofnodein the background, relaunched claude and so far so good.guidedways commentedon Jun 4, 2025
Spoke too soon :( 100% cpu usage again after a minute of work.
sepsi77 commentedon Jun 4, 2025
I'm using Claude Code inside of Cursor / VS Code and it seems to be a bit more reliable. I rarely get long freezes - it does freeze for maybe 30 seconds but always comes back to life. Node CPU usage does spike occasionally but not to very high levels.
tosh commentedon Jun 4, 2025
also seeing this on apple silicon macbook w/ claude code 1.0.10 in amd64 (rosetta) devcontainer with node 24.1
i think the issue is not present in earlier versions (e.g. 1.0.6?)
ashwin-ant commentedon Jun 4, 2025
Hey all, by any chance are you using any MCP servers? And can you share if they're using STDIO or SSE?
tosh commentedon Jun 4, 2025
@ashwin-ant only playwright-mcp, but haven't actively used the mcp in the session before or during the hang/freeze
arickuter commentedon Jun 4, 2025
Seeing the same on Ubuntu 22.04, after the latest claude code update.
21 remaining items
s00500 commentedon Sep 17, 2025
also experiencing lots of hanging today on 1.0.117
s00500 commentedon Sep 17, 2025
Nevermind, was not a claude code issue
mickg10 commentedon Sep 20, 2025
Out of curiosity, what was it?
mickg10 commentedon Sep 20, 2025
BTW - same thing on MacOS 26.
s00500 commentedon Sep 22, 2025
bash process that could not be killed due to a driver issue on a serialport...
yapishu commentedon Oct 2, 2025
Had a similar issue where it was interacting with a serial device that had to be unplugged to resume it
40960 commentedon Oct 14, 2025
Had a similar issue on:
Win11 25H2 26200.6584
Node.js v22.18.0
2.0.15 (Claude Code)
SR6560 commentedon Oct 31, 2025
lately by me it keep freezing, CPU not high
teeay-dev commentedon Nov 14, 2025
Very frequent, claude CLI practically not usable anymore on macOS 26.1. Codex, Gemini both happily work.
amosjyng commentedon Dec 7, 2025
I'm seeing this too now in the latest version 2.0.61
github-actions commentedon Jan 7, 2026
This issue has been inactive for 30 days. If the issue is still occurring, please comment to let us know. Otherwise, this issue will be automatically closed in 30 days for housekeeping purposes.
alexlloyd-apollo commentedon Jan 13, 2026
This issue is still occurring in v2.1.6
Krakazybik commentedon Jan 19, 2026
same issue on big files grep