Show HN: Agent Hand – Tmux session manager for AI coding agents (Rust)
https://weykon.github.io/agent-hand/
I was juggling 5+ Claude Code instances simultaneously. Four terminal windows, each with 3-4 tmux panes. "Which Claude is working on which task?" Wasting 10+ minutes just finding the right session.Built Agent Hand, a Rust rewrite of agent-deck with:
- Ctrl+N jumps to the most urgent session (waiting → ready → running) - Visual status from PTY output patterns (regex, no polling) - Sub-millisecond fuzzy search (Ctrl+G) - Dedicated tmux server (isolated from your default)
The WAITING state (!) is detected from prompt patterns like "Do you want to proceed?" The READY state () uses a TTL—if it was running recently and now idle, it's probably done.
MIT licensed. Would appreciate feedback on the PTY monitoring approach and any edge cases I'm missing.
https://github.com/weykon/agent-hand https://weykon.github.io/agent-hand/
(
2 comments
| on HN
)
I run 16-30 Claude Code sessions in parallel using an orchestrator I built (ComposioHQ/agent-orchestrator on GitHub). Session management is half the problem. The bigger problem is managing your own context around everything that's going on. Which agent is working on what, what's blocked, what just merged, what needs rebasing. The orchestrator is really an optimised human-in-the-loop process. It keeps me oriented so I can make decisions fast instead of spending 10 minutes figuring out what state everything is in.
Have you hit that yet or is this mostly focused on the monitoring side?