Interesting, but I wonder if this shifts too much complexity onto the user.
tmux is powerful, but not exactly approachable, and "multi-agent orchestration" on top of it feels like something that could get hard to reason about quickly. Curious how you think about UX here.
Tmux is pretty easy to pick up and build muscle memory by learning a few keyboard shortcuts from a basic youtube video and it's handy when you don't want to switch screens between multiple terminals just for one thing.
The ability to split and divide the screen pretty simply with a few keys is handy for anyone who spends enough time in a shell - the abilty to save that layout for the shell items you're using to load up easily again the next time is valuable too.
Multi agent orchestration likely just means keeping track of a few different windows all on one screen.
Good points and indeed thinking about this quite a bit. Currently leaning towards a CLI first approach so that Claude/Cursor/[insert coding agent] can configure and control the ide. Feels a bit meta, but also makes it extremely user-friendly.