4 people reported

All time, since Sep 24, including 2 thumbs-up on GitHub.

Orphan Claude processes left running

“It keeps running in the background for as long as VS Code is open: one extra process per workspace window, on every start.”

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/497/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

Orphan Claude processes left running after VS Code startup. Each window spawns an empty session process that is never stopped; /clear and loading from history also leave old processes alive.

Is this your bug?

File my report
Where
VS Code extension
Versions
2.1.281
Platforms
Linux, Windows
How bad
Breaks a normal workflow.

Part of: Leftover session processes pile up4 bugs

  1. Idle sessions keep processes alive7 people
  2. Idle sessions pin CPU core5 people
  3. Desktop memory and process buildup2 people

Not quite your bug?

  1. Desktop app missing sessions7 people
  2. claude.exe pins one CPU core after watched directory is deleted5 people

Original reports2, newest first

  1. #98639
  2. [Windows] VS Code extension still leaks orphan claude.exe processes in 2.1.281 (one per window at startup, plus /clear and loading from history)#96746

Do you work on Claude Code?

Claim its RAP Sheet to see what your users report and answer them in one place.