Zellij: A terminal workspace with batteries included

Original Article ↗ Hacker News Discussion ↗

Zellij, a Rust-based terminal multiplexer, is drawing attention as a more user‑friendly alternative to tmux, with features like floating panes, per-tab context, sandboxed plugins, and discoverable keybindings. Fans highlight its workflow improvements, session persistence, and ease of configuration, while skeptics question whether it offers enough beyond existing tools such as tmux, kitty, or terminal tabs and tiling window managers. Concerns also surface around input latency, memory usage, and keybinding conflicts, underscoring the trade-offs between modern features and the maturity and ubiquity of established tools.

Overall adoption vs. tmux/screen/terminal-only setups

  • Several users report switching from tmux to Zellij in recent months and being satisfied; others tried it briefly and went back to tmux.
  • tmux remains valued for ubiquity on remote systems, maturity, and powerful scripting/session tools (often with tmuxp).
  • Some still prefer GNU screen or Byobu (seen as “just tmux/screen defaults”).
  • A sizable group feels multiplexing belongs in the terminal emulator or window manager (e.g., Konsole, kitty, wezterm, tiling WMs) and rarely see a need beyond SSH persistence.

Floating panes & “zellij run” workflows

  • Floating panes are repeatedly described as Zellij’s “killer feature”:
    • Full-screen editor with ephemeral terminals for background tasks (tests, k9s, shells) that can be toggled via hotkeys.
    • Per-tab floating panes keep related tasks context-dependent.
  • The zellij run --floating command plus “press Enter to rerun” is praised for test-running and quick commands.
  • Skeptics argue tmux windows/panes/popups or just switching windows give similar benefits, questioning why overlays are better than separate windows.

Performance, latency & memory

  • Experiences diverge: some see no input lag; others report noticeable latency and sluggish scrolling on large monitors.
  • There are ongoing performance optimizations in upstream PRs.
  • Memory usage is contentious: some report Zellij using ~500MB and consider it unusable; maintainers attribute behavior partly to the Rust allocator and say memory is eventually freed, but users remain concerned about leaks.

UI, keybindings & usability

  • Zellij is praised for discoverability, simple config, visible contextual shortcuts, and focus on predictability.
  • The UI can feel too “big” or busy; documentation shows how to hide borders and reduce chrome.
  • tmux-style keybindings are supported and considered first-class, easing migration.
  • Others complain Zellij grabs too many keybindings and forces a mode/unlock model, adding friction.
  • Some note default bindings conflict with Emacs/readline; remapping is common.

Features, plugins & ecosystem

  • Liked features: session restore, sandboxed plugins (seen as a security win vs. tmux/nvim plugin ecosystems), true floating/stacked panes, multiplayer support.
  • Critiques: plugin ecosystem and advanced integrations (e.g., kitty image protocol) are still weaker than tmux + plugins.

Broader workflow debates

  • Ongoing arguments about whether multiplexers re-invent GUI IDEs and whether vim/neovim alone (with splits/tabs/terminal) suffice.
  • Many see detach/re-attach on remote hosts as the single unambiguous advantage of server-side multiplexers like tmux/Zellij.