Tutorial: eight commands to find orphaned Claude Code processes

In April 2026, a Claude Code user filed issue #43944 reporting that processes launched by the agent's Bash tool — such as dev servers, build jobs and test runners — kept running after the session ended. The report said they were "reparented to PID 1 (launchd on macOS) and continue running indefinitely," and it noted that orphaned processes can consume significant memory. Subsequent user reports put the figure at over 8GB of memory held by orphaned processes in some cases.

On November 6, 2026, DEV Community published a tutorial titled "Five agents running at once, fans spinning wildly: 8 commands to find the processes you should kill." The piece walks through eight commands for locating the process tree belonging to a finished task, rather than killing node processes that other agents are actively using. The author, who also maintains Hermes IDE, a workspace for developers building with Claude Code and other AI coding tools, frames the issue as a practical cleanup problem: multiple Claude Code sessions left behind dev servers, build processes and test runners whose parent shells had exited, so the surviving children get reparented to PID 1 and keep running until someone intervenes. The eight-command sequence is intended to identify which processes belong to which completed session before terminating anything, avoiding accidental kills of node processes still in use by other agents.