Sessions that survive disconnects

By default every connection goes over SSH, on TCP: if the network drops, the session is lost. Wendo can also use Mosh and Eternal Terminal (ET), which reconnect on their own.

Where to find it

When editing a connection, under Transport: Auto, SSH, MOSH, or ET. With Auto, Mosh is tried first, then ET, and if neither is available, SSH.

Mosh

It runs over UDP and survives network changes (from Wi-Fi to cellular data) and the phone going to sleep. If the server stops responding, the app tells you instead of closing the session.

On your computer you need:

• mosh-server installed, for example with brew install mosh or apt install mosh.
• UDP ports 60000–61000 open in the firewall.

In the connection you can change the port range, the path to mosh-server (for example /opt/homebrew/bin/mosh-server), and turn on “Use server IP for UDP”, which is useful when SSH goes through a proxy or a load balancer. In the terminal settings you choose how keys are displayed before the server confirms them (Mosh prediction).

ET (experimental)

It runs over TCP, on port 2022 by default. It needs etserver running on your computer and etterminal in the SSH session's path.

It is the only transport that survives the app being closed: the session appears in Home and, when you open it, picks up where it was.

Limits

• A Mosh session ends if the system closes the app, and it can't be resumed. If you need that, use ET or work inside tmux.
• Neither Mosh nor ET works with a Jump Host. With a Jump Host, use SSH.
• For a long scrollback history, work inside tmux.
• Mosh and ET are part of Wendo Pro. Without Pro, the connection goes over SSH.