Orchestrator, tmux-style split pane Claude sessions
Git worktree isolation per agent prevents merge conflicts unlike Conductor.

Declarative YAML config for agent teams, but tmux wrappers are common.
Terminal users running Claude Code agents
Cursor · Continue · tmuxp
Small OSS project that i created for myself and want to share with the community. It's a declarative, scriptable, terminal-based IDE focussed on agentic engineering.
That's a lot of jargon, but essentially its a multi-agent IDE that you start in your terminal.
Why is that relevant? Thanks to tmux and SSH, it means that you have a really simple and efficient way to create your own always-on coding setup.
Boot into your IDE through ssh, give a prompt to claude and close off your machine. In tmux-ide claude will keep working.
The tool is intentionally really lightweight, because I think the power should come from the harnesses that you are working with.
I'm hoping to share this with the community and get feedback and suggestions to shape this project! I think that "remote work" is directionally correct, because we can now have extremely long-running coding tasks. But I also think we should be able to control and orchstrate that experience according to what we need.
The project is 100% open-source, and i hope to shape it together with others who like to work in this way too!
Github: https://github.com/wavyrai/tmux-ide Docs: https://tmux.thijsverreck.com/docs
Git worktree isolation per agent prevents merge conflicts unlike Conductor.
Tmux + Claude Code + lazygit orchestration—tight workflow, but Claude Code adoption is unproven.
Automates Ghostty pane grids via keyboard simulation—solves real friction for tmux refugees.
Multi-agent tmux orchestrator with receipt ledger, but still early and narrow audience.
Solves RSI from cmd-tabbing between AI agent sessions and your terminal.
Claude Code talks to Codex via tmux panes using this CLI bridge.