Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix [Bug] claude process CPU spikes 50-100% when idle (regression in 2.1.108) [3 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#48748•Fetched 2026-04-16 06:52:04
View on GitHub
Comments
3
Participants
2
Timeline
10
Reactions
0
Author
jhamonjhamon
Participants
github-actions[bot]github-actions[bot]jhamonjhamon
Timeline (top)
labeled ×5commented ×3closed ×1renamed ×1

Starting with version 2.1.108, the claude process repeatedly spikes to 50–100% CPU even when idle between API calls. This does not occur in 2.1.104.

Root Cause

Starting with version 2.1.108, the claude process repeatedly spikes to 50–100% CPU even when idle between API calls. This does not occur in 2.1.104.

Fix Action

Workaround

Downgrading to 2.1.104 resolves the issue:

~/.local/bin/claude install 2.1.104

Code Example

~/.local/bin/claude install 2.1.104
RAW_BUFFERClick to expand / collapse

Description

Starting with version 2.1.108, the claude process repeatedly spikes to 50–100% CPU even when idle between API calls. This does not occur in 2.1.104.

Environment

  • Claude Code: 2.1.108 (regression), 2.1.104 (working)
  • OS: Ubuntu 24.04 (GCP e2-standard-2, 2 vCPU / 8GB RAM)
  • Shell: zsh, running inside tmux
  • Invocation: claude --dangerously-skip-permissions

Symptoms

  • claude process repeatedly spikes to 50–100% CPU as measured in htop, even when idle or waiting for API responses
  • Multiple Claude Code instances in tmux panes compound the problem, causing system-wide resource exhaustion in an environment that previously worked fine with multiple claude instances running in parallel

Steps to Reproduce

  1. Install Claude Code 2.1.108
  2. Run claude --dangerously-skip-permissions in a tmux session
  3. Observe CPU usage in htop — process spikes to 50–100% CPU even while waiting for user input or API responses

Workaround

Downgrading to 2.1.104 resolves the issue:

~/.local/bin/claude install 2.1.104

extent analysis

TL;DR

Downgrade to Claude Code version 2.1.104 to resolve the high CPU usage issue.

Guidance

  • The issue is likely caused by a regression introduced in version 2.1.108, as downgrading to 2.1.104 resolves the problem.
  • To verify the issue, run claude --dangerously-skip-permissions in a tmux session and observe CPU usage in htop.
  • Multiple instances of Claude Code in tmux panes can compound the problem, so limiting the number of instances may help mitigate the issue.
  • If downgrading is not feasible, consider running Claude Code in a resource-limited environment to prevent system-wide resource exhaustion.

Example

No code snippet is provided as the issue is related to a specific version of Claude Code and not a code-level problem.

Notes

The exact cause of the regression is not specified, and the provided workaround may not be suitable for all environments or use cases.

Recommendation

Apply the workaround by downgrading to version 2.1.104, as it is a known fix for the high CPU usage issue.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#api#parallel task#integration issue#index setup#retrieval issue

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING