Make Byobu Quiet Without Losing Its Window Menu

You will finish with Byobu's status indicators silenced while its window menu, keybindings and helper utilities remain available. The examples use Byobu 6.11, installed here as package version 6.11-0ubuntu1.1.

Allow about ten minutes. You need Byobu installed and a shell running as the same user whose Byobu configuration you want to change. This is a per-user change, not a system-wide setting, and it does not need sudo. The command reloads the current Byobu profile, so an existing session can change immediately.

1. Check the command before changing your session

Confirm the binary and package version first. This is read-only:

$ command -v byobu-quiet
/usr/bin/byobu-quiet
$ dpkg-query -W -f='${Package} ${Version}\n' byobu
byobu 6.11-0ubuntu1.1
$ man byobu-quiet
byobu-quiet [--undo]

Your path and package version may differ. The installed utility does not provide a separate --help option, so use its manpage for syntax. The manual documents only the ordinary form and --undo; there is no profile name, session name or status list to pass to this command. Run it as the ordinary user who owns the Byobu session. Using sudo would target a different user's configuration and can leave root-owned files behind.

2. Understand what quiet mode changes

byobu-quiet disables all of Byobu's status indicators and removes the normal hardstatus presentation. The window menu is preserved, along with Byobu keybindings and helper utilities. This is the useful distinction from a completely empty status area: you can still move between windows and use Byobu's controls.

The installed 6.11 script makes the change in the Byobu configuration directory selected by Byobu, normally ~/.byobu when that directory already exists, or an XDG configuration directory otherwise. It creates a marker named status.disable, removes existing lines containing hardstatus from the user keybindings file, adds a minimal hardstatus entry, and reloads the profile through the selected backend. Do not edit those files while the command is running.

This is configuration state, not a process-wide switch. It affects later Byobu starts for that user and can also refresh the current session. It does not disable tmux or GNU Screen, close windows, erase scrollback or alter the machine's service configuration.

3. Apply quiet mode

Run the command without elevated privileges:

$ byobu-quiet
$ printf 'exit status: %s\n' "$?"
exit status: 0

A zero status means the utility completed its file and profile-reload operations. The command normally prints no success message. Look at the Byobu session afterwards: the status indicators should be gone or reduced to the minimal window-menu presentation, while the window list and normal Byobu keybindings remain usable.

Do not treat the shell prompt as proof that the profile was reloaded. The reliable immediate check is the exit status captured directly after byobu-quiet. If you need to inspect the persistent marker, use a read-only command:

$ find "${BYOBU_CONFIG_DIR:-$HOME/.byobu}" -maxdepth 1 -type f -name status.disable -print
/home/you/.byobu/status.disable

The exact path depends on your Byobu configuration. If that find command prints nothing, do not guess a path and create the marker yourself; check the configuration directory Byobu is using and review any error output from the command.

4. Keep quiet mode separate from silent mode

Use byobu-silent only when you also want to remove the window list. Its manual says that it implies byobu-quiet. That is a more disruptive visual change because the menu you deliberately kept in the previous step will disappear.

If your aim is a less distracting Byobu session with windows still visible, use:

$ byobu-quiet

If you have already run byobu-silent, undoing the quiet state with byobu-quiet --undo may not restore every choice that silent mode made. Check the silent-mode configuration separately before relying on a rollback. Avoid stacking mode-changing commands while diagnosing a display problem.

5. Undo the change

Undo is safe to run as the same ordinary user:

$ byobu-quiet --undo
$ printf 'exit status: %s\n' "$?"
exit status: 0

On this version, --undo removes the status.disable marker and reloads the profile. It does not require a reboot and does not delete your Byobu windows. Start a new Byobu session, or refresh the current one if its backend has not visibly restored the normal indicators.

The undo operation is not a backup restore. The utility removes its marker, but its 6.11 implementation also edits the user keybindings file when applying quiet mode. If you had custom hardstatus lines there, save that file before experimenting so you can compare it afterwards. Do not blindly replace the whole configuration directory: that can discard profiles, colours, keybindings and other personal settings.

6. Diagnose the common failures

If the command exits non-zero, capture the status immediately and inspect the configuration directory and current backend without changing them:

$ byobu-quiet
$ status=$?
$ printf 'byobu-quiet status: %s\n' "$status"
byobu-quiet status: 1
$ printf 'backend: %s\n' "${BYOBU_BACKEND:-not set}"
backend: not set

The numeric result is useful evidence, but this manpage does not define a portable table of error codes. Read any diagnostic printed by the command, then check that the configuration directory is writable and that a supported backend is installed and available. Do not add sudo as a first response: it can make the change for root instead of for the user whose session you are fixing.

If the indicators remain, reload the Byobu profile through the normal session controls or start a fresh session, then check whether the marker exists. If the window menu has disappeared, you may have used byobu-silent; undo that command's related state according to your local configuration rather than repeatedly toggling both commands.