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.
Hacker News (Newest) files mainly under programming. We currently carry 5,306 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | tmpfs /home/stan |
| Canonical URL | https://blog.angeloff.name/post/2026/05/29/teaching-tmux-to-babysit-my-claude-code-agents/ |
| Publication time | Fri, 29 May 2026 18:09:53 +0000 |
| Retrieval time | 2026-05-29T18:20:02.626Z |
| Last seen | 2026-05-29T18:20:02.626Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | oAmuiL9BLH-S |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
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
