[BUG] Incredibly slow performance
Status Closed — not planned
Maintainer reply ✓ Yes — ant-kurt
Activity 15 comments · opened Sep 5, 2025 · closed Feb 11, 2026
💡 Likely answer: A maintainer (ant-kurt, collaborator)
responded on this thread — see the highlighted reply below.
Environment
- Platform (select one):
- [ X ] Anthropic API
- Claude CLI version: 1.0.102
- Operating System: Windows 11
- Terminal: PowerShell
Bug Description
PowerShell constantly freezes the main thread on script lookup, making @ script reference next to useless. Running in YOLO mode is especially slow. To note to similar posts, my local settings are 1kb, with a few more kb for agents. Claude.MD is also within the recommended size
15 Comments
Found 3 possible duplicate issues:
This issue will be automatically closed as a duplicate in 3 days.
🤖 Generated with Claude Code
How large is your project directory? Does your
/doctoroutput show Search is OK, do you see errors withripgreporrgonclaude --debug?Hi! Experiencing the exact same issue. Claude Code periodically freezes so severely that it's impossible to even type characters from the keyboard. The lag is unbearable - keystrokes take several seconds to register, making the
tool practically unusable during these freeze periods.
This happens randomly but frequently throughout sessions, regardless of project size or complexity. The freezing affects all input, not just @ script references.
Additionally, there's no way to exit with ESC after successfully creating a subagent - the interface becomes unresponsive and you have to wait for it to timeout or force close the terminal.
Windows 10, latest Claude Code version 1.0.105 - 1.0.107. The performance degradation is severe enough to significantly impact productivity.
Can you share a bit more info about your configurations @thePostFuturist @kolkov:
DISABLE_AUTOUPDATERenv var (can use~/.claude/settings.json)I had gilded ClaudeCode session running for several days. I was in the superstitious place - not want to reboot my machine, etc. The Claude got into a loop on something (no messages back, just a "doing ...." equiv message that never came back. It wouldn't response to esc, and crtl-c did nothing, so I had to kill a process. I rebooted after that cos why not - even a ChromeBook Plus with 32GB or ram benefits from that. The new session with Claude is at least 10x slower, it's lost understanding of the codebase and I'm missing the one I had a few days ago :( It's also objectivelt dumber:
Re JS and Jest:
No Claude, in no universe is any jest test ever to have
expect(true).toBe(true);and when I point that out to you don't accept it, try something, then revert back to it when you couldn't get a single test working (using a test to get to a root cause in prod-code) after 10 mins.I have to agree about slower and slower performance. When looking at network communication, I cannot see any traffic during the pause, indicating a "sleep(long_time);"
Got the same issue.
Can also report it is extremely slow on Windows 11, I can use the cli only on a new 16-core system with ok-ish performance. Laptops all freeze up all the time.
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.
PWSH 7.5, GoLand. NPM.
Same on Windows 11 (non-WSL, command prompt only) Claude Code 2.1.4. Only started happening this week. Changing back to a project I touched a week ago, which was performing fine, is now unbearably slow as well, so it's a recent issue with the client (there have been no Windows Updates here). Installation method was via NPM, IIRC.
This issue has been automatically closed due to 60 days of inactivity. If you're still experiencing this issue, please open a new issue with updated information.
This issue was closed incorrectly despite recent human comments. This behavior of the bot is reported at https://github.com/anthropics/claude-code/issues/16497. Please upvote that issue, so maybe it gets noticed.
The Anthropic team decided that ignoring the community was the best tactic...
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.