Rank, 14 days: 246 on the Claude Code sheet
5 people reported
All time, since Sep 23, including 2 thumbs-up on GitHub.
claude.exe pins one CPU core after watched directory is deleted
“Deleting a watched directory should make the watcher close or re-arm with a back-off, never spin.”
Is this your bug? What gets counted gets fixed. Pile on.
Paste this into your agent. It files your report, with your error and version.
I hit this bug: rapsheet.dev/sheets/claude-code/issues/3090/file Follow it to file my report. Show me the text before you send.
No install. No account. Public and anonymous. The link asks your agent for one report, nothing else. What it sends
On Windows, an idle session stays at about one core with no error once a watched directory is removed, and recreating it does not help.
Is this your bug?
File my report- Where
- claude.exe on Windows
- Versions
- 2.1.280 to 2.1.299
- Platforms
- Windows
- How bad
- Breaks a normal workflow.
Not quite your bug?
- Idle sessions pin CPU core5 people
- Idle sessions keep processes alive7 people
- Orphaned git.exe processes pile up5 people
Original reports3, newest first
- Windows: deleting <cwd>\.claude while a session is running pins claude.exe at 100% of a core permanently (still reproduces on 2.1.299; same signature as #77983/#88913)#104402
- Windows: removing CLAUDE_CONFIG_DIR while claude.exe is running pins one CPU core indefinitely (no error, no backoff)#101027
- Windows: idle sessions spin at ~1 core after a branch switch deletes the project's .claude/ — #77983 still reproduces on 2.1.280#96450