tmux vs zellij (and wezterm, and shpool): an honest comparison
Zellij's pitch is real: discoverable keybindings on screen, sane defaults, no config required. So why does this site exist for tmux anyway? Because the answer depends on which of four things you actually need — here's the honest matrix.
What zellij genuinely does better
Out-of-box experience, by a mile. The status bar shows available keys contextually, so you never google "how do I split"; defaults include mouse support and sane scrollback; floating panes and layouts are first-class. If tmux's learning curve is the reason you don't multiplex, zellij removes it. It's good software.
What pulls people back to tmux
Four things, per every "I switched back" post: ubiquity (tmux is a 1MB-ish install on every distro and already on most servers; muscle memory works everywhere), scripting (send-keys, capture-pane, format strings — zellij's CLI actions are younger and thinner), ecosystem (resurrect, fzf integrations, sessionizers, a decade of answers), and resource footprint. The keybinding-collision problem zellij spent releases fixing simply doesn't exist in tmux's prefix model — one key is sacrificed, everything else passes through.
The terminal-native option
kitty, WezTerm, Ghostty, and iTerm2 all do splits and tabs natively with perfect scrollback, native copy-paste, and zero latency overhead — locally, that's genuinely nicer. What they can't do: survive SSH disconnects (the session lives in the GUI process), attach from a different machine, or run on the server itself. If you never SSH anywhere and never need a session to outlive its window, you may not need a multiplexer at all.
Special mention: shpool and mosh
If persistence is the *only* thing you want — no splits, no windows — Google's shpool gives you detach/reattach with native terminal scrolling, and mosh solves flaky connections (roaming, laptop sleep) at the transport layer. mosh + tmux is a classic pairing: mosh keeps the pipe alive, tmux keeps the sessions.
The actual recommendation
Work on remote servers or need sessions that outlive terminals → tmux; the 20-line sane config erases most of its default hostility, and it's the skill that transfers everywhere. Local-only and allergic to configuration → zellij, or honestly just your terminal's splits. Building automation around terminal sessions (CI, agents, scripted workspaces) → tmux, nothing else is close. And whichever you pick: the concepts (sessions, panes, detach) transfer — none of this learning is wasted.
Verified against tmux 3.6 · updated July 2026 · more guides · cheat sheet