tmux for AI agents — without the raw terminal.
tmux keeps a session alive so your agent survives a dropped SSH pipe. Termdeck does that for Claude Code and Codex — then adds what a terminal multiplexer can’t: per-tool approvals, rendered diffs, push to your phone, and one board across every machine. Detach from the terminal, reattach from any device, no forked session.
tmux + ssh vs. Termdeck
| tmux + ssh | Termdeck | |
|---|---|---|
| Keeps the session alive | Yes | Yes |
| Built for | Any shell | AI coding agents |
| Tool-call approvals | Raw prompt in the pane | Allow / deny UI, survives refresh |
| Diff review | Plain text scrollback | Every edit rendered as a diff |
| Reach you when it’s blocked | No | Push to your phone |
| Mobile-friendly | Tiny terminal on a phone | Installable PWA |
| Many machines at once | One pane at a time | One sidebar + fleet board |
| Two-writer safety | Manual | Lock prevents forked sessions |
Keep tmux for your shells. Use Termdeck for your agents — it complements the terminal, it doesn’t replace it.
tmux vs Termdeck, answered
Can I just run Claude Code inside tmux?
You can, and the session survives a dropped connection. But tmux only holds a terminal — you still get raw approval prompts, plain-text diffs, and no way to be paged when a run blocks. Termdeck keeps the session alive and adds the approval UI, diffs, and push on top.
Is Termdeck a tmux replacement?
No — keep tmux for shells and servers. Termdeck is the layer for coding agents: it streams Claude Code and Codex to the browser, survives refreshes, and lets you take over from any device.
Can I detach from the terminal and reattach on my phone?
Yes. Close the terminal client and drive the same session from the web or your phone. A live-registry lock stops two writers from forking it, so takeover is safe.
Does it manage more than one agent?
Yes. Every machine and session shows up in one sidebar and a fleet board, with an attention badge on the runs waiting for you — no cycling through panes.