Nicholas Clooney

blog: Messy Chat with Your Agents? You Just Need One More. Really.

I published Messy Chat with Your Agents? You Just Need One More. Really., about splitting the Claude agent I talk to from the one coordinating work on my Stone Age remake. With tmux-agents, the new main agent has one peer: the coordinator, which handles the main Codex agent and its sub-agents. The post shows the setup before and after, why my conversation got quieter, and the extra hand-off that comes with it.

Earlier in thread

Nicholas Clooney

feature: tmux-agents v1.0.0

I shipped v1.0.0 of tmux-agents, extracted from my dotfiles with its full history and released under MIT, because I want my sub agents' work to stay visible after the task ends. Each Claude or Codex sub agent runs in its own tmux window: I can watch a live preview, switch in to steer it, and let agents exchange tasks and replies through tmux-ask. The panes stay until closed, the conversations can be resumed afterward, and a line above the status bar flags agents that need me. There's also a setup skill so an agent can install it and walk me through a quick start.

A request from Claude arriving in Codex's pane Codex's reply arriving back in Claude's pane
Claude asks Codex for a review, and the reply comes back as a new message.
The agent list showing sub agents with their status and parent, and a live preview of the selected session A hidden Codex sub agent opened in a popup from the list
prefix + a lists the sub agents with a live preview. I can open one in a popup to answer it or give direction.
#tmux-agents#tmux#ai-agents#tooling#workflow