[BUG] Session pegs a full CPU core indefinitely after its worktree is deregistered
Status Closed — not planned
Reported on v2.1.226
Maintainer reply None cached
Activity 3 comments · opened Aug 8, 2026 · closed Aug 23, 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?
Repro shape: a wt-cleanup session removed its own worktree registration; the directory remained but git worktree list no longer showed it; the session then spun
Ended only by Stop-Process -Force
What Should Happen?
Dispatch should stop repeatedly replying.
Error Messages/Logs
Measurements: 43,961 CPU-seconds over 14.7 hours, sustained 1.07 CPU-sec per wall-second, zero output. Survived the Dispatch STOP — so it's independent of that bug
Steps to Reproduce
a wt-cleanup session removed its own worktree registration; the directory remained but git worktree list no longer showed it; the session then spun
Claude Model
Opus
Is this a regression?
No, this never worked
Last Working Version
_No response_
Claude Code Version
2.1.226
Platform
Anthropic API
Operating System
Windows
Terminal/Shell
PowerShell
Additional Information
Claude Code (native CLI): 2.1.226
Claude Desktop: 1.26832.0.0
Bundled CLI: 2.1.222
OS: Windows 11 Home 10.0.26200
Model: Opus 5
This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗