[BUG] CPU usage spikes to 100% and becomes unresponsive after ~10 interactions when statusLine command is configured

Status Fixed / completed
Reported on v2.1.34
Maintainer reply None cached
Activity 3 comments · opened Feb 6, 2026 · closed Feb 9, 2026

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?

When configuring a statusLine with a command property in ~/.claude/settings.json, Claude Code becomes unresponsive after approximately 10
interactions, with CPU usage spiking to 100%.

The command line tool used for the status line is claude_code_statusline.

What Should Happen?

Claude Code should continue to respond normally regardless of the number of interactions, even with statusLine.command configured.

Error Messages/Logs

CPU usage spiking to 100%.

Steps to Reproduce

  1. Install claude_code_statusline
  2. Add a statusLine configuration with a command field to ~/.claude/settings.json:

``json
{
"statusLine": {
"command": "cc_sline"
}
}
``

  1. Start Claude Code
  2. Interact with Claude Code approximately 10 times

Claude Model

Opus

Is this a regression?

Yes, this worked in a previous version

Last Working Version

_No response_

Claude Code Version

2.1.34

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

iTerm2

Additional Information

_No response_

View original on GitHub ↗

3 Comments

github-actions[bot] · 8 months ago

Found 3 possible duplicate issues:

  1. https://github.com/anthropics/claude-code/issues/19019
  2. https://github.com/anthropics/claude-code/issues/23008
  3. https://github.com/anthropics/claude-code/issues/22509

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

byplayer · 8 months ago

It looks fixed.

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