tmux 3.0 Arrived in 2019

The tmux project released version 3.0 in late 2019, advancing the terminal multiplexer’s release line after the 2.x series. Despite the visually large version jump, tmux’s own FAQ cautions that its version number has no special significance: it is not a semantic-versioning declaration that every major number means a ground-up redesign.

What users should read instead of the first digit

tmux evolves through changes to commands, formats, options, terminal-feature handling, and compatibility. The authoritative record is the release changelog and manual for the installed version. Configuration copied from a different release may use an option that was renamed, removed, or assigned different behavior.

That was particularly relevant around the 2.x and 3.x generations, as old configuration snippets circulated for years. A responsible upgrade begins with:

tmux -V
tmux -f /dev/null new-session

The first command identifies the actual binary. The second can help distinguish a base tmux problem from a failure caused by user configuration. Existing sessions continue to belong to the server process that created them, so testing a new binary may also require stopping or isolating the old server deliberately.

The stable idea behind changing releases

The core architecture remained the same: a persistent server owns sessions, windows, panes, and their pseudoterminals; clients attach and detach. Release 3.0 refined a mature, already well-established tool rather than changing that fundamental client-server model in any structural way.

This makes tmux a useful example of why version interpretation must come from a project’s documented policy. A number that resembles semantic versioning is not evidence that semantic versioning applies, just as a zero-major release does not automatically mean unusable software.

What actually shipped in 3.0, concretely

Beyond the version number itself, 3.0’s changelog includes format expansion support in the load-buffer and save-buffer commands, a new rectangle_toggle format variable, set-hook -R to run a hook immediately rather than waiting for its triggering event, pane-focus hooks, mouse-resize handling fixed to correctly target the intended pane in more layouts (including resizing multiple panes simultaneously), and new x/X commands in choose-tree for killing sessions, windows, or panes directly from that interface. None of these individually resembles a “breaking, ground-up redesign” — they’re the kind of incremental, additive changes that accumulate in any actively maintained tool’s changelog, which is exactly the point the FAQ entry is making about not over-reading the version number.

The tool tmux was explicitly positioned against

tmux exists in a lineage stretching back to GNU Screen, originally written by Oliver Laumann and Carsten Bormann at Technische Universität Berlin and first published in 1987, addressing the same core need decades earlier: letting a user switch between multiple tasks on a single physical terminal, and detach from and later reattach to long-running sessions. Screen’s maintenance passed to Jürgen Weigert and Michael Schroeder around 1990, who moved it under the GNU Project and added scrollback, split-screen, and session-sharing features over the following years. tmux’s own creator has been explicit that dissatisfaction with Screen’s aging, hard-to-extend codebase was a direct motivation for writing something new rather than continuing to patch the older tool — 3.0’s steady, incremental changelog is a continuation of that same “cleaner, more maintainable alternative” premise tmux launched with in 2007, refining rather than reinventing the same fundamental multiplexer concept Screen had already established and popularized decades earlier among Unix and Linux users working across long-running, often unreliable remote sessions. Related: Fixing SSH Sessions That Don’t Know the Terminal’s Actual Size · Fixing tmux Keybinding Conflicts With Your Terminal or Shell

Sources: