[BUG] CPU usage spikes to 100% with statusLine command configured (regression of #23609)

Resolved 💬 2 comments Opened Feb 9, 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?

This is a regression of #23609, which was reported as fixed and closed on 2026-02-09.

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 same issue that was previously fixed in #23609 has resurfaced on the latest version (2.1.37).

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
  3. Observe CPU usage spiking to 100% and Claude Code becoming unresponsive

Claude Model

Opus

Is this a regression?

Yes, this was fixed in #23609 but has resurfaced

Last Working Version

The fix for #23609 was working briefly before this regression

Claude Code Version

2.1.37

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

iTerm2

Additional Information

Original issue: #23609 (closed as fixed on 2026-02-09)

View original on GitHub ↗

This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗