Teaching tmux to babysit my Claude Code agents
The article discusses the author's experience of managing multiple Claude Code agents using tmux. It highlights the challenges of keeping track of agent statuses and introduces a solution that visually indicates which agents need attention. The author shares their custom configuration that uses colored dots in tmux to represent the state of each agent.
- ▪The author runs multiple Claude Code sessions simultaneously, each in its own tmux window.
- ▪Managing several agents can become cumbersome, leading to confusion about their statuses.
- ▪The author developed a tmux configuration that uses colored dots to indicate whether an agent is blocked or finished.
Opening excerpt (first ~120 words) tap to expand
Teaching tmux to babysit my Claude Code agents May 29, 2026 If you are like me, you no longer run one Claude Code session — you run a small fleet. One window is building a feature in a TypeScript monorepo, another is reviewing a colleague’s pull request, a third is chasing a redraw bug in a Neovim plugin. tmux makes this easy: a window per agent, Alt + 1–9 to jump between them. Often they are not even different projects — just git worktrees of the same repo, one agent per branch. ✦Dictated, not typed — but read. I thought this post out loud and transcribed it, then wrote it up with Claude Code, which had direct access to the code and config it describes. I read every word; the ideas and direction are mine, the prose a collaboration. The trouble starts at three or four agents.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at tmpfs /home/stan.
Discussion
0 commentsMore from tmpfs /home/stan
