JackMBurch

Kill Claude Code Processes — Design skill for Claude Code

Design community

Terminal UI for reviewing and stopping Claude Code background session processes, including the pre-warmed spares agent view never shows.

How to install Kill Claude Code Processes

This entry records only its repository, not the path inside it, so there is no exact command to give. Open JackMBurch/kill-claude-code-processes and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Kill Claude Code Processes does

Terminal UI for reviewing and stopping Claude Code background session processes, including the pre-warmed spares agent view never shows.

Alternatives in Design

  • Theme Factory — Style artifacts with professional themes including 10 pre-set color/font combinations 94.1k ★
  • NotebookLM Automation — Complete programmatic access to Google NotebookLM—including capabilities not exposed in the web UI 6.8k ★
  • Design Review Workflow — by Patrick Ellis - A tailored workflow for enabling automated UI/UX design review, including specialized sub a 3.7k ★

README

kill-claude-code-processes

A small terminal UI for reviewing Claude Code's background session processes and stopping the ones you no longer want running.

 ▐▛███▛█   kcc v0.2.0
▝▜██████▀  6 total
  ▝▝ ▝▝    4 holding a process

 AGE   LIVE  STATUS       NAME                             DIR                    ID
 5d    yes   Needs input  flaky test triage                ~/src/api              a1b2c3d4
 2d    yes   Done         changelog for the 2.4 release    ~/src/api              b2c3d4e5
 3h    yes   Working      migrate the config loader        ~/src/web              c3d4e5f6
 12m   yes   Spare        (pre-warmed spare, no conversa.. ~/src/web              d4e5f6a7
 9d    -     Done         bump the lockfile                ~/src/tools            e5f6a7b8
 21d   -     Needs input  dependency audit                 ~/src/tools            f6a7b8c9

Why

Claude Code's agent view has no key that stops a session's process while keeping its row. `Ctrl+X` on a finished session has nothing to interrupt, so the row stays exactly as it was, and pressing `Ctrl+X` twice deletes the row instead. The only real lever is `claude stop ` from a shell, which means looking up ids by hand.

Two things this shows that agent view does not:

  • Whether a session actually holds a process. The row label describes the conversation, not the process. A Done session can still own a live worker, and a session that owns nothing looks identical.
  • Pre-warmed spares. The supervisor keeps booted workers in reserve so a new chat opens instantly. They hold a process, have no conversation, and never appear as a row, so agent view cannot show you your real process count.

Install

Needs Python 3 and the `claude` CLI on `PATH`. No other dependencies.

curl -fsSL https://raw.githubusercontent.com/JackMBurch/kill-claude-code-processes/master/install.sh | sh

That fetches the single `kcc` file into `~/.local/bin`. Set `KCC_BINDIR` to put it somewhere else. The i