Show HN: I built a tmux-style split pane Claude sessions during an interview

Yesterday, during a YC company's interview, the CTO asked me to claude up "a claude code thing where he can have like 5 different claudes and see them at a glance"

I cooked something up during the interview, but I realized this was actually kind of useful and kept going after.

Anyways,

Orchestrator(tbh I named this pretty arbitrarily) is a desktop app that lets you run multiple Claude Code agents side by side in split panes, tmux style (it even uses tmux style BSTs!!). Each agent gets its own git worktree, and you can see potential merge conflicts, token usage, etc. in real time.

Basically, the main usecase is that, if you want to have 6 claudes running side by side, working on different things, and you want deep observability into each claude (unlike conductor), but you also want to prevent merge conflicts, orchestrator is probably your best bet right now.

I don't have an apple developer license, so you need to clone and build the repo yourself, but if someone is willing to sponsor or help build this using their developer signing key thing, I can package it into a dmg so more people can install it.

Also, fun fact, orchestrator was built using orchestrator :p

Show HN: I built a tmux-style split pane Claude sessions during an interview
github.com

Wait this is really helpful for my daily workflow Love the screenshot in the github repo

Okay so it's basically free bridgeswarm. Love it

yea tmux and i3 (and probably other kind of window managers) use some kind of binary search tree/tree structure to manage splits.

https://github.com/tmux/tmux/blob/master/layout.c https://github.com/tmux/tmux/wiki/Getting-Started https://i3wm.org/docs/userguide.html#tree

I think the biggest thing is, this is a native claude code orchestrator, and doesn't pretend to be a terminal at the same time

This uses worktrees to manage different claude code instances, so you don't get one claude overwriting another one's work, and predicts potential merge conflicts when you're merging different worktrees by tracking file diffs across claudes.

TBH, if you're only working like 2/3 claudes, a regular CLI will probably work; but if you're scaling up to like 10 different instances that's another story.