Your agents keep running when you sleep.
Manage 20+ AI coding sessions in parallel. Terminal sessions that survive disconnect, reachable from your phone, with state that announces itself.
Sign in
What this is
Persistent
Close your laptop. Your agents keep working. Reattach from anywhere.
Phone-reachable
Open the URL on your phone, see your sessions, type, swipe back.
State-aware
Color-coded dots tell you which agent finished, which is grinding, which is waiting on you.
What it actually does
Terminal Orchestrator is a browser front-end on top of tmux. Every session you start runs inside a persistent tmux pane on your host. The web app attaches over a Rails ActionCable channel, streams the pty bytes to xterm.js, and replays scrollback when you reconnect. Close the tab. Walk away. Switch devices. The shell — and everything running in it — stays exactly where you left it.
Who this is for
It is built for people who run long-lived agentic processes and refuse to lose them to a flaky Wi-Fi handover. Claude Code, OpenAI Codex, aider, ttyd-style remote shells, Neovim with a half-hour LSP warm-up, a curl that has been streaming logs for an hour, a Rails console mid-debug. If you have ever come back to a dead SSH session and felt the rage of starting over, this is for you.
Why persistence matters
Modern coding agents are long-running by design. A single Claude Code run can grind for ten minutes; a multi-step Codex plan can run for thirty. The traditional answer — tmux inside SSH inside a terminal emulator — works until your laptop sleeps, your VPN flaps, or you need to switch to the phone to check a build. Terminal Orchestrator decouples the shell from the viewer. The shell lives on the server. The viewer is just a tab.
How it works
- Add a project — point it at a directory on your host.
- Open a session — a tmux pane spins up and attaches in your browser.
- Walk away — the session keeps running. Open the same URL on your phone to reattach.
Common questions
- Is this hosted, or do I run it?
- You run it. Single-tenant by design — one user, your host, your tmux. There is no shared SaaS instance and no shared filesystem.
- What happens if the server reboots?
- tmux sessions do not survive a reboot. Terminal Orchestrator records which sessions you had open and offers to recreate them on next launch, but in-flight processes are gone — same as raw tmux.
- Does it work on a phone?
- Yes. The mobile layout has full keyboard and scrollback, and the state-aware dots on the session list let you triage which agent is stuck or finished without opening each one.
- How is this different from Warp, Wave, or ttyd?
- Warp and Wave are local terminal emulators. ttyd is a tmux-over-websocket viewer with no session list, no auth, no state detection. Terminal Orchestrator gives you a multi-session dashboard, browser auth, and agent-state awareness on top.