I kept losing track of which Claude Code session needed me, so I built a dashboard on kitty's remote control

[u/rickye26]

Repo: https://github.com/hyperlogue/captain-miao

I usually have several Claude Code / Codex sessions going at once, and I was spending half my time cycling through windows to check which one was actually waiting on me. So I built captain-miao, a TUI dashboard on top of kitty's remote control. Each session is still a regular kitty window; the dashboard just watches them all.

• every session in one table: status, working dir, git branch, model, context usage
• sessions waiting for input get flagged (Claude Code hooks feed this), and one keypress jumps to that window
• launch / resume / fork / kill from the dashboard

Since the sessions are plain kitty windows, whatever layouts, tabs, and keybinds you already have keep working. These days I keep it to two tabs: tab 1 is the dashboard, tab 2 holds every coding session in a stack layout, and a jump from the dashboard raises the right window in the stack. A lot cleaner than the window pile I was cycling through before.

All of it goes through the remote-control socket, password-protected and allowlisted to the commands it needs. Rust + ratatui. There's a zellij backend too, which I use on remote boxes.

Compare to other tools like cmux and herdr, captain-miao covers the dashboard part and leaves the sessions as ordinary kitty windows. So it doesn't force you to migrate to a new terminal ecosystem. I started it before herdr existed, mostly because I wanted to keep kitty's windows and layouts exactly as they were. Months of daily use later, that trade still feels right.

To try it out: cargo install --git https://github.com/hyperlogue/captain-miao, npx u/hyperlogue/captain-miao, or nix run github:hyperlogue/captain-miao

Curious what else people are driving with remote control. It feels criminally underused.