21–30 of 49 posts
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.
If this supported Gemini and Codex I would find it useful. I never run more than one Claude, it's always a mix.
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.
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.
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.
I'm also trying to build something similar for agent orchestration where one terminal is controlling multiple terminals. I tried using tmux but it's very good at sending the initial text to the tmux sessions, but I've not been able to get an agent to have a proper back and forth controlling multiple tmux sessions. I know we can use send-keys, but reading the session or knowing when that session is complete is kind of…
It supports tmux, but you can use it without via embedded terminal. It also has native integration with a few select terminals that expose the right kind of APIs.
Installs as single binary (written in Go) with no external dependencies.
I'm so married to my existing tmux workflows and layout that I'm not sure whether I'd ever feel open to trying out something like this. At the same time, orchestrating multiple agents with native tmux and git worktree does feel cumbersome.
From my perspective, this is cool, but since tmux is kind of permanent, you open your layout, set 1,2,3 screens for agents, you might add gemini and opencode. then open vite for server and one for shell for example. Then you can just close it and reopen whenever you want to work on it.
And that is it. If I am missing something, processes taking memory or such, I have a machine with memory (I know, flexing how expensive things are), please explain.