Troubleshooting

Three rules shape almost everything on this page, and knowing them explains most of what you will run into.

You always get connected

A missing dependency never blocks the connection. It degrades. SSH is the floor transport, a bare shell is the floor experience, and the terminal stays fully usable behind any banner.

Plain language, not stderr

Moshpit says what is missing, what it costs you, and how to install it. A raw command not found is a bug, not a message.

Nothing happens behind your back

No silent installs. No silent session creation. No quietly attaching the other multiplexer because the one you picked isn’t there.

Note

Three surfaces to read before anything else.

The banner at the top of the terminal. One slot, one banner at a time, always dismissible. Precedence is fixed: a dead mosh return path outranks the roaming banner, which outranks the degraded-host banner.

The transport pill in the top bar. It reads SSH or MOSH when live, MOSH · roaming while roaming, reconnecting with an amber dot, or offline with a red one. A dropped session is visible, not silent.

Long-press that pill on a mosh session. You get MOSH DIAGNOSTICS — four raw counters, meant to be screenshotted and sent, not admired.