Agent Session Attention Board
When running dozens of Claude Code sessions in the terminal, see at a glance which one needs you
- Problem
- Heavy agentic-development users manage 30+ Claude Code sessions in tmux but struggle to quickly identify which session is stuck, which is waiting for input, and which is done. Sometimes they only remember a name or phrase from a conversation and can't find the right session.
- Solution
- A tmux-native read-only dashboard that scans all running Claude Code sessions, flags ones needing attention (waiting for input, error, done), supports full-text keyword search across conversation history, and fits vim-style navigation.
- Users
- Senior developers and AI engineers running many Claude Code sessions in parallel
- MVP
- List all Claude Code sessions in local tmux; status flags (waiting/running/done/error); keyword search across session content; vim keybindings; read-only without interfering with sessions
- Revenue
- Open-source core plus paid Pro (multi-machine aggregation, notifications, history search index); or a one-time desktop license
- Why now
- Agentic development is moving from single-session to parallel multi-session workflows, and terminal users lack a lightweight board. A solo developer is the target user and can validate quickly with tmux and local logs.
Source discussions · 1
- Hacker NewsShow HN: ccfleet, a quiet, tmux-native Claude Code dashboard1↑ 0