Install byobu with Homebrew, apk, apt, dnf, MacPorts, Nix, zypper

Project links

• Homepage
• Repository
• Upstream docs
• Package manager page

Commands and aliases

• byobu
• byobu-config
• byobu-ctrl-a
• byobu-disable
• byobu-disable-prompt
• byobu-enable
• byobu-enable-prompt
• byobu-export
• byobu-janitor
• byobu-keybindings
• byobu-launch
• byobu-launcher
• byobu-launcher-install
• byobu-launcher-uninstall
• byobu-layout
• byobu-prompt
• byobu-quiet
• byobu-reconnect-sockets
• byobu-screen
• byobu-select-backend
• byobu-select-profile
• byobu-select-session
• byobu-shell
• byobu-silent
• byobu-status
• byobu-status-detail
• byobu-tmux
• byobu-ugraph
• byobu-ulevel
• col1
• ctail
• manifest

Project history

The upstream README describes Byobu as originally designed to make the plain but practical GNU Screen experience more elegant for the Ubuntu server distribution. Later releases added support for tmux while keeping Screen support, which made Byobu less a single multiplexer and more a curated terminal environment.

Dustin Kirkland is listed by the project as the primary author, with Nick Barcet, Raphael Pinson, and Derek Carter credited as emeritus authors. The project has long lived in the Ubuntu and Launchpad ecosystem while also accepting contributions through its GitHub repository.

Adoption history

Byobu became familiar to Ubuntu Server users because it packaged multiplexer defaults, status lines, and helper commands into a batteries-included command. Its presence across Homebrew, Debian, Ubuntu, Fedora, Alpine, MacPorts, Nix, and openSUSE packaging shows that the tool escaped its Ubuntu origin and became a general Unix terminal convenience.

Its adoption is tied to users who wanted persistent remote sessions without hand-maintaining large Screen or tmux configuration files. Byobu's value was not inventing multiplexing, but standardizing a useful opinionated profile that distributions could ship.

How it is used

Users typically launch `byobu` to start or attach to a managed Screen or tmux session, then use Byobu's keybindings and status widgets for windows, system information, and session control. The bundled commands such as `byobu-config`, `byobu-select-backend`, `byobu-enable`, and `byobu-disable` make it scriptable and friendly to login-shell workflows.

The documented configuration search path uses `$BYOBU_CONFIG_DIR`, `$XDG_CONFIG_HOME/byobu`, and `~/.byobu`, so package users can keep personal status, keybinding, and backend preferences outside the system installation.

Why package nerds care

Byobu matters in package-manager culture because it is a wrapper that made two already-packaged workhorses, Screen and tmux, feel like a coherent product. It is the kind of package server people install immediately after provisioning a host because it smooths daily SSH work.

It is also a good example of distro-born tooling becoming cross-platform: an Ubuntu Server nicety that Homebrew and other Unix package ecosystems carry because the workflow is useful everywhere.

Timeline

• 2008: Byobu emerges from Ubuntu Server work around enhanced GNU Screen profiles.
• 2009: The project is known publicly as Byobu and shipped broadly in Ubuntu-era server workflows.
• 2011: tmux support becomes central enough that Byobu is described as supporting both GNU Screen and tmux.
• 2023: The upstream README still presents Byobu as a maintained cross-distribution multiplexer layer for Linux, BSD, and macOS.

Related projects

• GNU Screen is the original terminal multiplexer Byobu enhanced.
• tmux is the modern multiplexer backend Byobu also supports.
• Ubuntu Server and Launchpad are part of Byobu's historical packaging and contribution context.

Sources

• https://byobu.org/
• https://github.com/dustinkirkland/byobu/blob/master/README.md
• source_facts.package-manager