which-claude-code

which-claude-code

Auto-generated session titles + per-session colors in the Claude Code statusline.

If you run several Claude Code sessions in parallel terminals, you've probably
asked yourself: *which tab was the one fixing the auth bug? which was the one
writing tests?* This plugin answers that question automatically, without you
having to name anything.

After every prompt you submit, a tiny background Haiku call distills your
intent into a 3-6 word title. It shows up in the statusline, tinted with a
color uniquely hashed from the session ID. Same session = same color, forever.
Different sessions = visually distinct at a glance.

The trailing ctx: / 5h: / 7d: segments show current context-window,
five-hour, and seven-day usage. Each segment renders only when Claude Code
provides the corresponding field, so older builds are unaffected. A
freshly-reset window shows .txt. The hook itself
   returns in ~10ms so your prompt is never delayed.

2. Statusline (bin/statusline.sh) — reads that file on every render,
   printing ●   ·  ·  (). The title is colored from a
   20-color palette, indexed by cksum(session_id), so the mapping is stable
   for the life of the session.

State lives under ~/.claude/which-claude-code/ (overridable via
$WHICH_CLAUDE_CODE_STATE_DIR). Nothing else is touched.

Defensive note for maintainers — recursive Claude subprocess calls

If you fork this plugin or write a similar one: read this.

Any hook that shells out to claude -p (or any Claude Code subprocess) can
trigger unbounded recursion. The child claude -p inherits the user's
~/.claude/settings.json and enabled plugins, so its own UserPromptSubmit
event fires — re-invoking the same hook, which spawns another claude -p,
and so on. Detached and disowned, the chain survives the user closing…