Compositing vs mirroring
Two ways a terminal multiplexer gets its programs onto the screen. Both keep programs alive in a background server. Compositing, the tmux model, works out what every pane should look like and paints it into one screen of text, borders and status bar included, so any terminal can show it, locally or over SSH. Mirroring is the Rex model: the server sends each program's raw output to a smart client that runs a real terminal engine per program, and the client catches up from the server after a disconnect.
Trade-offs, as reemus lays them out (Nov 2026):
- Compositing runs a terminal inside a terminal, with the multiplexer as a middleman. Text selection across panes grabs the wrong lines, mouse input has to pass through it, newer features such as images have to be reinterpreted, and mitchell-hashimoto adds that it puts a slow layer in front of a fast terminal.
- Mirroring gives native selection, input and rendering on every device, Mac or phone. It needs the client app on every screen, you can't attach from an old terminal over SSH, and on a slow connection it is worse than tmux because every byte goes to every client.
Mirroring predates rex: WezTerm shipped a native client for a mux server in 2019, and VS Code keeps its terminals alive in a background process (2021). Rex builds on libghostty, Ghostty's terminal engine as a library, and herdr moved to the same pattern with herdr-core and a desktop app in October 2026.
Source: report