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.
Wait this is really helpful for my daily workflow Love the screenshot in the github repo
Haha thanks for liking it!!
Also orchestrator is MIT licensed :p so feel free to break it apart and play with it
what's the difference between this and other tools like cmux, mux, superset or something else? are there any notable advantages i can refer to?
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.
Okay so it's basically free bridgeswarm. Love it
I've never used bridgeswarm before but from the looks of it yea!
Thanks for liking it :D
tmux style BSTs?
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