plain-language glossary
what is a terminal multiplexer?
TL;DR
A terminal multiplexer like tmux or Zellij runs several terminal sessions in one window: split panes, tabs, and sessions that keep running after you detach. It handles layout, not agent work, so worktrees, diffs and review are still up to you. Herdr applies the multiplexer idea to agents. Pane sits a layer higher, as a desktop workspace with worktrees, diffs and git review built in.
A terminal multiplexer lets you run several terminal sessions inside one terminal window. You can split the window, switch tabs, and often detach from a session while its processes keep running. tmux and Zellij are classic examples. Herdr applies the same terminal idea to agent work. Pane sits one layer higher, with a desktop workspace for agents, worktrees, diffs, and git review.
the category in one table
A multiplexer arranges shells. An agent manager tracks the work inside them.
| need | terminal multiplexer | agent manager |
|---|---|---|
| many shells | split panes and tabs | named agent sessions |
| detach | server or session keeps running | client reconnects to workspace state |
| worktrees | you create and clean them | managed around an agent task |
| diff review | run git or another tool | built-in visual review in Pane |
| remote work | SSH or a remote session | self-hosted daemon or agent server |
what it actually does
Layout, sessions, detach and reattach. Nothing about branches or diffs.
The word sounds grander than the job. A multiplexer owns terminal layout and session attachment. It gives you one place to split shells, name windows, move between tasks, and reconnect later. It doesn't automatically know which branch belongs to which agent or which diff is ready for review.
- → layout: split one terminal into several panes
- → sessions: keep a group of shells together
- → detach: leave the client while the server keeps running
- → reattach: connect to the same live session later
Herdr is a multiplexer with an agent focus
Herdr is the multiplexer idea rebuilt around agents.
Herdr keeps the terminal at the center, then adds agent status, workspaces, integrations, mouse controls and remote session paths. Its server keeps live processes running after a client detaches, which makes it a good fit for agents on a remote server. After a full restart, the saved layout returns and supported agents can resume their own conversations. Since August 2026 it also runs natively on Windows.
- → use the TUI when terminal control is what you want
- → use the background server for live detach and SSH reconnect
- → check integration support before expecting native agent resume
- → keep restart recovery separate from live process persistence
Pane is an agent manager
Pane owns the worktree, branch, ports, status and diff around each terminal.
Pane includes terminals, but it also tracks the work around each terminal. A pane can own a worktree, branch, port, environment, status, and diff. That matters when three agents are editing three tasks and you need to decide what ships.
- → use Pane for worktree and branch ownership
- → open visual diffs without leaving the workspace
- → run git actions from keyboard shortcuts
- → connect to a remote daemon when the host should do the work
a simple decision workflow
Name the problem first: layout, live detach, per-agent review, or a remote host.
Name the problem before you pick the tool.
- 1If you only need shell layout, start with tmux, Zellij, or Windows Terminal.
- 2If you need live terminal detach and reattach around agents, look at Herdr and tmux-based workflows.
- 3If every agent needs a worktree, branch, status, and diff review, look at an agent manager such as Pane.
- 4If the work must run elsewhere, choose the host and connection path, then install the agent and its credentials there.
keep reading
Sources
- Corrections
- If anything here is wrong or out of date, tell us and we'll fix it and update the date at the top. Open an issue on GitHub
- Sources
frequently asked questions
By Parsa Khazaeepoul, co-founder of Pane. .