[BUG] Performance regression in v2.0.72 - slow input/response with ~30k tokens context
Preflight Checklist
- [x] I have searched existing issues and this hasn't been reported yet
- [x] This is a single bug report (please file separate reports for different bugs)
- [x] I am using the latest version of Claude Code
What's Wrong?
Description:
Environment:
- Claude Code version: 2.0.72
- OS: Linux (RHEL 8)
- Memory: 32GB
- CPU usage during issue: ~111%
Issue:
After upgrading to newer versions of Claude Code, experiencing significant lag when:
- Typing input
- Waiting for response rendering
This was not an issue in older versions. The slowdown occurs even at ~30k tokens context (not just 100k+).
Observed behavior:
- claude process consumes 111%+ CPU
- Input feels sluggish
- Response takes longer to render/display
What Should Happen?
Expected behavior:
Performance similar to older versions - responsive input and fast rendering.
Error Messages/Logs
Steps to Reproduce
Environment:
- Claude Code version: 2.0.72
- OS: Linux (RHEL 8)
- Memory: 32GB
- CPU usage during issue: ~111%
Normally use claude code , it will become slow soon .
Claude Model
None
Is this a regression?
Yes, this worked in a previous version
Last Working Version
_No response_
Claude Code Version
2.0.72
Platform
Anthropic API
Operating System
macOS
Terminal/Shell
Terminal.app (macOS)
Additional Information
_No response_
19 Comments
Found 3 possible duplicate issues:
This issue will be automatically closed as a duplicate in 3 days.
🤖 Generated with Claude Code
Confirming this regression (slowdown + request failures), but I’m not 100% sure which exact version introduced it.
I didn’t use Claude Code CLI on Tuesday. I started using it again on Wednesday evening, and at that time my installed version was 2.0.72. Since then, everything feels noticeably slower (general responsiveness + longer time to get outputs).
Additional detail on the request failures:
Request timed out. Check your internet connection and proxy settingsThis seems correlated with session/context growth: once it reaches some threshold, requests start timing out/failing, and compaction resets it back to a workable state.
If helpful, I can share sanitized logs / list enabled plugins & hooks.
I also want to mention that I’m using the Max / Pro plan, so other plans might encounter even more severe issues than I do.
+1 - Experiencing the same issue
Environment:
Symptoms:
API Error (Request timed out.)retrying up to 10/10 attempts/compacttemporarily helps, but timeouts return quickly after first editAPI_TIMEOUT_MSto 600000ms (shown in retry message), but still timing outWorkaround attempts that didn't help:
API_TIMEOUT_MSin.claude/settings.json/compact(only temporary relief, bugs return after first/second message)/clear(works but loses context, bugs return after first/second message)*Downgraded now, working just fine in v2.0.70 as suggested by another github user.
The workaround doesn't work since compaction fails most of the time due to too long conversation if you apply a large plan (sometimes we cannot break things up). 2.0.72 is unusable.
May be related to these reported performance issues, but just running
claudein the terminal to kick Claude Code off hangs indefinitely on Windows. Previously versions started up immediately.We're looking into this folks - bear with us. I don't have a repro yet but downgrading _sounds_ reasonable.
Downgrading doesnt work. It keeps auto updating
On Thu, Dec 18, 2025 at 6:55 PM Chris Lloyd @.***>
wrote:
you need to set
in global
~/.claude/settings.jsonNope. It ignores it. And got tricked into auto update. Will post a detailed
bug about it.
On Thu, Dec 18, 2025 at 7:04 PM Vasyl @.***> wrote:
This bug is really bad. The ignore auto update also doesn't work like blackholegalaxy mentioned.
Temporary workaround - Downgrade via npm:
My solution was to install the previous version via npm:
npm install -g @anthropic-ai/claude-code@2.0.71 && ~/path/to/npm/packages/claude --version && ~/path/to/npm/packages/claude
In my case with nvm:
npm install -g @anthropic-ai/claude-code@2.0.71 && ~/.nvm/versions/node/v20.19.2/bin/claude --version && ~/.nvm/versions/node/v20.19.2/bin/claude
To find your npm global path:
npm root -g
# or
which claude # if already in PATH
To prevent auto-updates, add to ~/.claude/settings.json:
{
"env": {
"DISABLE_AUTOUPDATER": "1"
}
}
⚠️ Note: For some reason, DISABLE_AUTOUPDATER is being ignored in my case. As a quick workaround, I created a shell alias that reinstalls the stable version each time:
alias claude='npm install -g @anthropic-ai/claude-code@2.0.71 && ~/.nvm/versions/node/v20.19.2/bin/claude'
Edit:
Clarification: I also have the native/official installer version installed, but I'm forcing the use of the npm version by explicitly calling the npm binary path instead of the default claude command.
Edit 2:
Environment:
| Component | Version |
|-----------|----------------------------------------------------|
| OS | Ubuntu 25.04 (Plucky) |
| Kernel | 6.14.0-37-generic |
| Arch | x86_64 |
| Node.js | v20.19.2 |
| npm | 11.4.2 |
| Shell | Bash |
| Terminal | Terminator (also tested on Alacritty/Gnome Terminal - same issue) |
The issue reproduces across different terminal emulators, so it's not terminal-specific.
Same!
I am having the same issue here
+1 Claude 2.0.73 - crazy high CPU usage with lagging starting in the first 5-10 minutes of a session.
Also can confirm downgrading to 2.0.71 solves the problem. Thank you @nasatome
Still occurs on 2.0.73
so, still waiting on 2.0.71
Confirming this issue with additional diagnostic data from extensive debugging session.
Environment
Symptoms
/exitcommand takes 30+ seconds to registerCritical Evidence: NOT a Network Issue
curl -I https://api.anthropic.comsucceeds instantly with HTTP/2 200Debugging Attempts (None Resolved the Issue)
ANTHROPIC_TIMEOUT=120000ANTHROPIC_DISABLE_HTTP2=1.wslconfig~/.claudeand~/project/.claudedirectoriesclaude /login.claudeignoreto excludenode_modules/,data/, etc.Project Context
.claudeignorewas added).claudeignore)Reproduction
Workaround
Downgrading to 2.0.71 resolves the issue (as original reporter noted).
Hypothesis
Something in the 2.0.71 → 2.0.72 change is causing the Node.js event loop to block, possibly related to:
.claudeignoreThis is a severe regression that makes 2.0.72 completely unusable on Linux/WSL2 with larger projects.
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.
still waiting on 2.0.71