← multiplexers directory○ community

Multiplexer · Wez Furlong

Wezterm.

Wezterm collapses the terminal-plus-multiplexer stack into a single binary. The multiplexer is just there, scripted in Lua, and it ships with sane defaults that respect 2026 conventions.

$ brew install --cask wezterm

The interesting design choice in Wezterm is that the multiplexer is not a separate program; it is the terminal itself. Splits, tabs, persistent sessions, and remote multiplexing are all native. For anyone who has ever wished tmux and the terminal emulator were not two different programs that need to be configured separately, Wezterm is the answer.

It also happens to be a really good terminal emulator on its own. GPU-accelerated, ligature-friendly, configurable in Lua. Even without the multiplexer features, it would still be on a shortlist of credible terminals.

§01What you get

The integrated multiplexer is the headline, but the surface is broader than that:

  • Native multiplexing, with splits and tabs that need no separate tmux or zellij layer.
  • Lua config, which is powerful and approachable, and lets the config file include real logic rather than just key-value pairs.
  • SSH multiplexing. Connect to a remote machine and the local UI hosts panes that run there. Cleaner than tmux-over-ssh.
  • GPU rendering, smooth on big scrollbacks, large fonts, and ligatures.
  • Cross-platform. macOS, Linux, Windows, with the same config everywhere.

§02Where it fits

Wezterm is the right call when one tool for the terminal-plus-multiplexer job is what the workflow wants. It is especially good for remote work, because the SSH multiplexing is genuinely better than running tmux remotely. The UI is local, only the work is remote, and disconnects do not lose state.

§03Setup

brew install --cask wezterm    # macOS

# config in:  ~/.wezterm.lua
# minimal start:

local wezterm = require 'wezterm'
return {
  font = wezterm.font 'JetBrains Mono',
  font_size = 13,
  color_scheme = 'Tokyo Night',
  hide_tab_bar_if_only_one_tab = true,
}

§04Caveats

  • Less "multiplexer culture." When collaborating with people who use tmux or zellij, the workflow does not map directly, and shared scripts will not transfer.
  • Lua is not for everyone. Powerful, but a one-line config is not what the language gives you.
  • Newer keybindings. Wezterm's defaults are not tmux's, and ten years of muscle memory does not transfer for free.