## 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 fo

[Bug] claude process CPU spikes 50-100% when idle (regression in 2.1.108)

Status Fixed / completed

Reported on v2.1.108

Maintainer reply None cached

Workaround ✓ Mentioned in description ↑

Activity 4 comments · opened Apr 15, 2026 · closed Apr 16, 2026

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

Install Claude Code 2.1.108
Run claude --dangerously-skip-permissions in a tmux session
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

View original on GitHub ↗

4 Comments

github-actions[bot] · 6 months ago

Found 3 possible duplicate issues:

This issue will be automatically closed as a duplicate in 3 days.

If your issue is a duplicate, please close it and 👍 the existing issue instead
To prevent auto-closure, add a comment or 👎 this comment

🤖 Generated with Claude Code

jhamon · 6 months ago

While there may be shared root causes, I do not think this is a duplicate of these older issues from January/February because the problem only appeared sometime after 2.1.104. I did not test with all versions between 2.1.104 and latest to pinpoint the origin.

jhamon · 6 months ago

seems resolved now on latest

github-actions[bot] · 5 months 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.