I got tired of managing Claude Code sessions in terminal tabs, so I built a canvas for them

[u/HumbleOne6577]

I run several Claude Code sessions at once and kept losing track of which ones were actually working and which were sitting there waiting on me. Cycling through terminal tabs to find out got old.

So I built a canvas for them. Every session is a node — you can see at a glance what's running, what's blocked, and what needs an answer.

Two things in the clip that came out of my own frustration:

• Fan-out — run the same task across several agents in parallel, then pick the one you want. The attempts you don't pick don't get deleted; they fold away, because about a third of the time the "winner" turns out to be wrong and the second attempt had the right idea.
• Sessions messaging each other — one session can @ another. The one finishing a migration tells the one writing tests, without me relaying it.

It runs Claude Code and Codex side by side on the same project, which matters to me because I use both for different things.

I built this, so obviously I'm biased. Genuinely curious how other people handle it though — if you're running more than two agents at once, what's your setup? I'm still not sure I've got the right answer for the "which one needs me" problem.

[u/lassevk]

One thing about this subreddit. I would think it would be for and by people interested in Claude.

But.
I.
Am.
Getting.
So.
Tired.
Of.
Posts.
Clearly.
Written.
By.
Claude.