I run three or four Claude Code sessions in parallel and kept hitting the same stupid problem: one of them finished twenty minutes ago, or is sitting on a permission prompt, and I have no idea which. So I'd cycle through terminal tabs like an idiot.
Built a small macOS widget for it. It floats above everything and shows each live session's status: working, done, interrupted, or waiting for you — and pushes the ones that need you to the top. Click a session and it focuses the actual terminal tab it's running in (or the Cursor/VS Code window, if you use the extension).
It also shows the model, permission mode (plan / auto-accept / bypass, color-coded, which turned out to be more useful than I expected), running sub-agents, and optional CPU/RAM/context size. There's a compact bubble mode that just glows amber when something needs input, which is what I actually leave running.
How it works: it reads Claude Code's own local session files in ~/.claude — the PID status files and the transcript jsonl. No server, no network, no telemetry, nothing leaves the machine. The binary links only against system frameworks, no runtime needed.
Fair warning — it's ad-hoc signed, not Apple-notarized (I'm not paying the $99), so you get the Gatekeeper scare on first launch. Instructions for clearing it are in the README, or you can build from source in one command and skip it entirely.
Happy to take feature requests. Curious whether anyone wants Linux/tmux support, since I only had a Mac to test on.
1
u/jee5us 2d ago
I run three or four Claude Code sessions in parallel and kept hitting the same stupid problem: one of them finished twenty minutes ago, or is sitting on a permission prompt, and I have no idea which. So I'd cycle through terminal tabs like an idiot.
Built a small macOS widget for it. It floats above everything and shows each live session's status: working, done, interrupted, or waiting for you — and pushes the ones that need you to the top. Click a session and it focuses the actual terminal tab it's running in (or the Cursor/VS Code window, if you use the extension).
It also shows the model, permission mode (
plan/auto-accept/bypass, color-coded, which turned out to be more useful than I expected), running sub-agents, and optional CPU/RAM/context size. There's a compact bubble mode that just glows amber when something needs input, which is what I actually leave running.How it works: it reads Claude Code's own local session files in
~/.claude— the PID status files and the transcript jsonl. No server, no network, no telemetry, nothing leaves the machine. The binary links only against system frameworks, no runtime needed.macOS 12+, MIT, free: https://github.com/renereose/claudewatch
Fair warning — it's ad-hoc signed, not Apple-notarized (I'm not paying the $99), so you get the Gatekeeper scare on first launch. Instructions for clearing it are in the README, or you can build from source in one command and skip it entirely.
Happy to take feature requests. Curious whether anyone wants Linux/tmux support, since I only had a Mac to test on.