Skip to content

Settings

Settings are opened with Ctrl+, or the gear control in the top bar. Changes apply immediately to open terminals. Session logging is the exception and saves explicitly, because storage policy should not change under a running recorder.

The settings dialog The settings dialog
Eight sections, listed on the left. The footer states when changes apply.

Appearance

  • Application theme: light, dark, or follow the system.
  • Interface scale: the size of the whole window. Terminal text has a separate zoom (Ctrl+Shift+= / Ctrl+Shift+- / ++ctrl+wheel++).
  • Terminal colour scheme: fifteen schemes, grouped into light and dark sets.
  • Font: family, size and line height. JetBrains Mono and the Nerd Font symbols are bundled; any other family must be installed on the machine.

Terminal

Terminal settings Terminal settings
Cursor, clipboard behaviour and scrollback settings.
  • Cursor: block, underline or bar, blinking or not.
  • Right-click: copy-selection-otherwise-paste (the terminal convention), always paste, or a context menu.
  • Copy on select and the multiline paste confirmation.
  • Scrollback lines kept per terminal.
  • Local shell: the shell a local terminal starts; auto uses the login shell.

Session logging

Off by default. This section enables retention globally, controls whether input is captured, and sets the storage policy: location, maximum total size, minimum free space (absolute and percentage), maximum age, and the number of parts each session keeps. Current usage against the quota is displayed here.

Session logging settings Session logging settings
The only section with explicit Save buttons, marked with a dot in the nav when it has unsaved edits.

More on session history

Highlighting

Global keyword rules applied to every terminal: keyword, foreground, optional background, case sensitivity and whole-word matching. Hosts can add their own rules or replace the global set.

Keyword highlighting rules Keyword highlighting rules

Behavior

Tab behaviour, including confirm before closing a live session, which is on by default because closing a connected tab ends its shell, and the restore switches, both on by default: automatically reconnect remote sessions — restoring a workspace dials its remote tabs, and a dropped connection redials a few times on its own; turn it off to restore remote tabs without logging in — and restore terminal history, which saves recent output locally every few seconds and replays it above the new session after a restore or reconnect.

Keyboard

Controls whether new splits continue the current session (on by default; SSH reuses the live connection, and serial always asks), a summary of the layout keys, and access to the full shortcut editor.

The keyboard shortcut sheet The keyboard shortcut sheet
The shortcut sheet: search commands, add or replace chords, and view conflicts.

All commands share one keymap. A chord is recorded by pressing it, a command can carry a second chord, and defaults are restored in one click. The sheet is also reachable with Ctrl+Shift+/.

Every default chord

Backup & data

Create backup writes the Muxus-side data to a file: folders, colours, saved Telnet/serial hosts, workspaces, tunnels and preferences. Restore a backup merges a file back in; items absent from the file are not deleted.

Export OpenSSH writes the SSH hosts out as a standard ssh_config for use with another client. Muxus-only settings remain in the backup.

What a backup excludes

Private key files, passwords and recorded session history are never part of a backup.

About

Version and platform information, a link to the source repository, and a manual update check. When a newer release exists, Muxus links to its GitHub release so the appropriate installer can be downloaded.