# Paneflow vs tmux

> Paneflow is the local workspace for supervising coding agents with panes, branches, diffs, dev servers, and read-only MCP context. tmux is the terminal multiplexer for durable sessions, SSH, headless systems, and deep terminal automation.

URL: https://paneflow.dev/compare/tmux
Raw Markdown: https://paneflow.dev/compare/tmux.md
Last updated: 2026-07-02

## Highlights

### Start with visible agent panes

Split panes with Cmd/Ctrl+Shift+D, change focus with Alt+Arrow, and select text with the mouse. No prefix or .tmux.conf required.

### Track agent work, not just processes

Paneflow launches CLI agents in dedicated panes and shows which ones are working or waiting for your input. tmux runs those commands like any other terminal process.

### Keep code context beside terminals

Paneflow keeps branches, diffs, and dev servers beside your panes. tmux stays a terminal multiplexer; you can script context around it, but it does not model it.

## The important differences

Use the table to check the boundary: Paneflow owns local agent supervision; tmux owns durable terminal sessions.

| Topic | Paneflow | tmux |
|---|---|---|
| Primary job | Local workspace for coding agents | Terminal multiplexer for sessions, windows, and panes |
| Coding agents | Dedicated panes, status, read-only MCP pane context | Runs CLI agents as ordinary terminal processes |
| Branches, diffs, dev servers | Built in | Script around tmux |
| SSH / headless sessions | Graphical desktop app, no detach/reattach server | Core strength: detach, reconnect, run in any TTY |
| Automation | CLI, JSON-RPC, read-only MCP tools | CLI, control mode, hooks, formats, capture-pane, send-keys, pipe-pane |
| License / package size | GPL-3.0-or-later, roughly 13-21 MB by platform/package | ISC, tmux 3.7b source archive roughly 0.79 MB |

Versions checked July 2, 2026: Paneflow v0.7.6. tmux 3.7b, released July 1, 2026. Both free: Paneflow GPL-3.0-or-later, tmux ISC.

## Which tool should you use?

Choose by the job that must survive all day: agent supervision or terminal persistence.

### Choose Paneflow if

- Your work happens on a local desktop with a graphical workspace
- You supervise several coding agents and need panes, branches, diffs, and dev-server state together
- You want agents to read other panes through Paneflow's read-only MCP bridge
- You want a native app around real terminals, not a TUI inside another terminal

### Choose tmux if

- You SSH into remote servers and need sessions that survive disconnects
- You work on headless servers, containers, serial consoles, or a Raspberry Pi
- You automate your terminal heavily with capture-pane, pipe-pane, send-keys, hooks, formats, or control mode
- You need the smallest portable Unix multiplexer more than an agent workspace

## When to keep tmux

Keep tmux when one of these requirements matters more than local agent supervision:

- SSH and remote servers. tmux sessions survive disconnects. Paneflow has no remote-session support.
- Headless or embedded systems. Paneflow needs a graphical desktop and a GPU-capable rendering stack. tmux runs in almost any TTY: Raspberry Pi, Docker, KVM console, or serial port.
- Heavy terminal automation. tmux exposes commands like capture-pane, send-keys, and pipe-pane, along with hooks, formats, and control mode. Paneflow's JSON-RPC and MCP interfaces focus on workspace and agent control.
- Maximum portability or smallest footprint. tmux is very lightweight and runs on many systems. Paneflow is a graphical app available today on Linux, macOS, and Windows.

## Frequently asked questions

### Can Paneflow replace tmux for local development?

Yes, for local agent-oriented development on Linux, macOS, or Windows. It is not a replacement for SSH detach/reattach; keep tmux for that.

### Does Paneflow preserve running processes like tmux?

No. Paneflow restores the environment around your shells: panes, layouts, working directories, custom names, and terminal history. It does not keep processes alive after the app closes. tmux process persistence comes from its separate server and detachable session model.

### Can I use my .tmux.conf with Paneflow?

No direct migration. Paneflow uses a JSON file (paneflow.json) with a different schema. The keybinding idea is similar, but most tmux options have no equivalent because Paneflow is not a multiplexer running inside another terminal. See the schema reference.


## Choose based on your environment

Working locally with multiple agents? Download Paneflow or read the getting-started guide. Spending your days on SSH or headless servers? Keep tmux and check its GitHub repository or man tmux.