[BUG] CPU usage spikes to 100% and becomes unresponsive after ~10 interactions when statusLine command is configured
Resolved 💬 3 comments Opened Feb 6, 2026 by byplayer 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
- Install claude_code_statusline
- Add a
statusLineconfiguration with acommandfield to~/.claude/settings.json:
``json``
{
"statusLine": {
"command": "cc_sline"
}
}
- Start Claude Code
- 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_
This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗