Tmux-IDE, OSS agent-first terminal IDE
Declarative YAML config for agent teams, but tmux wrappers are common.
Tmux for claude code
Git worktree isolation per agent prevents merge conflicts unlike Conductor.
Developers using Claude Code for multi-task workflows
Conductor · Claude Code
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
Declarative YAML config for agent teams, but tmux wrappers are common.
Ghostty-powered native macOS terminal built specifically for managing parallel Claude Code sessions.
Multi-agent tmux orchestrator with receipt ledger, but still early and narrow audience.
Automates Ghostty pane grids via keyboard simulation—solves real friction for tmux refugees.
Solves RSI from cmd-tabbing between AI agent sessions and your terminal.
Tmux + Claude Code + lazygit orchestration—tight workflow, but Claude Code adoption is unproven.