Mulmoterminal

Run multiple Claude Code and Codex sessions in parallel — and see which one needs you.

sessions side by side, each in its own cell, with the one that needs you marked in colour. Vibe

track of which is waiting. Sessions survive a reload (tmux), work isolates in git worktrees ,

Every cell is a real pty. htop , lazygit , a dev server and Claude Code are the same kind

a shell or a yarn dev launcher can sit in the same worktree an agent is working in.

The grid, live — each cell coloured working , done or needs you .

90 seconds, with sound: one agent, then a grid of them. Zoom into one and the roster still holds what every other session asked, answered and did, so you go to whichever is lit and lose nothing catching up.

When you ran one coding agent, the slowest thing in the room was the agent.

Now that you run five, the slowest thing in the room is probably you.

One of them is always stopped. A permission prompt. A question. Until you notice, it does nothing at all.

MulmoTerminal puts every session on one screen. Blue is working. Green is done. Amber is waiting on you.

The other kind of slow is: what did I even ask this one? The roster keeps one line per session — what you asked, and what came back. Nothing left to remember.

Then you pick the next one from whatever is lit. Click, answer, move on. You never go looking — the roster tells you.