FAQ¶
Does Muxus change my ~/.ssh/config?¶
Only when you choose OpenSSH config storage. A new SSH host can instead be saved in
Muxus app data only, and MobaXterm/SecureCRT imports offer the same choice. OpenSSH
edits rewrite that block and nothing else, atomically, leaving a .muxus.bak of the
previous contents.
Will ssh on the command line still work?¶
Yes for hosts stored in OpenSSH config. Muxus-only database hosts are intentionally private
to the app and do not appear to ssh, scp or rsync.
Do I need to import my hosts?¶
No. Every concrete Host block in the configuration is present in the sidebar on first
launch, including the files it pulls in with Include.
Why do some options in my config seem to be ignored?¶
Match blocks are skipped, because their conditions depend on runtime state Muxus does not
reproduce. Everything in Host blocks is resolved, and unmodelled keywords are preserved
verbatim. See ssh_config support.
Does it support 2FA / keyboard-interactive?¶
Yes, as a dialog labelled with the hop that issued the prompt. Agent, certificates, keys with passphrases, keyboard-interactive and passwords follow the OpenSSH order.
Can I use it as a web terminal on a server?¶
No. It binds 127.0.0.1, checks a per-run token and the Origin header, and is designed
as a single-user local tool. Do not put it behind a reverse proxy.
Where is my data?¶
The application database is in the platform data directory (~/.local/share/muxus/,
~/Library/Application Support/Muxus/, %APPDATA%\Muxus\). Muxus-only host settings are
stored there; OpenSSH-backed hosts remain in ~/.ssh/config. See the
CLI reference.
Are my passwords stored anywhere?¶
Not by default. Passwords are transient unless Remember this password is selected on an SSH password prompt. A single hidden keyboard-interactive field explicitly labelled as a password is treated the same way, which covers network devices that use keyboard-interactive for password login. Remembering creates the platform-independent password vault and writes authenticated ciphertext to the local database. The prompt policy can use the OS credential store (the default), ask once at startup, or ask whenever a credential is needed. The master password is always required to view or edit the saved value and is never stored. Private-key passphrases, 2FA codes and all other keyboard-interactive answers are never remembered. See the security model.
Why is session logging off by default?¶
Recording terminal output is opt-in. Enable it globally or per host. Commands that are typed are echoed back as remote output, so pause logging before displaying secrets. See session history.
Images do not render. What is wrong?¶
Check that the remote tool is emitting a supported protocol: kitty graphics, sixel or
iTerm2. Tools usually detect support from TERM and terminal queries; Muxus advertises
xterm-256color and answers the cell-size queries icat uses. A single transmission over
64 MiB is rejected. See images in the terminal.
Why is Ctrl+W not "close tab"?¶
Ctrl+W deletes a word in the shell, and Muxus does not take keys the shell needs. Closing is Ctrl+Shift+W (Cmd+W on macOS), and tabs use Alt+1 … Alt+9. Any binding can be changed in the shortcut sheet.
Does splitting a pane log in twice?¶
No. A split continues the current session over the same SSH connection, so there is no second login and no second 2FA prompt. This is configurable in Settings → Keyboard.
Can I keep a tunnel open without a terminal?¶
Yes. Saved tunnels hold their own transport lease, so closing every terminal to that host leaves the tunnel running.
Does it work on Windows?¶
Yes: SSH, Telnet, local shells and COM serial ports. The desktop installer is an NSIS
.exe.
Is there a Wayland/HiDPI/scaling issue?¶
Interface scale is a setting (Settings → Appearance), separate from terminal font zoom, so the UI and the text are sized independently.