How does Eternal Terminal compare to ssh, autossh, and mosh?

Updated

Eternal Terminal (ET) is a remote shell that automatically reconnects without interrupting the session. It uses ssh to initialize the connection, but unlike ssh it can survive network outages and IP roaming. Compared with autossh, ET keeps the same session alive instead of starting a new one on each reconnect; compared with mosh, ET supports native scrolling and tmux control mode (tmux -CC). Choose ET if you want a persistent remote shell that survives network changes and works with tmux control mode; choose ssh if you only need a basic remote terminal, autossh if a fresh session per reconnect is acceptable, or mosh if you don't need native scrolling or tmux -CC.

What each tool does

Tool Core behavior Session after network outage Notes from the source
ssh Standard remote terminal program Session dies; you must kill it and reconnect ET uses ssh to initialize the connection
autossh Automatically restarts an ssh session when it detects a reconnect Reconnects, but starts a new session each time Described as a more advanced version of while true; ssh myhost.com
mosh Popular alternative to ET with the same core functionality Reconnects Does not support native scrolling or tmux control mode (tmux -CC)
ET Remote shell that automatically reconnects without interrupting the session Session survives network outages and IP roaming Inspired by ssh, autossh, and mosh

Key differences that affect your choice

Connection setup

ET is not a from-scratch replacement for ssh at the transport level: it uses ssh to initialize the connection. So you still rely on ssh for the initial handshake, then ET takes over the persistent session behavior.

Surviving outages and IP roaming

With ssh, after a network outage you must kill the ssh session and reconnect. ET sessions can survive network outages and IP roaming, so the session continues rather than being torn down.

Reconnect behavior

Autossh will automatically reconnect, but it starts a new session each time. The source gives a concrete consequence: if you use tmux with control mode, you must wait for the ssh connection to die and then re-attach. ET instead maintains your tmux session even when the TCP connection dies and resumes quickly.

tmux and scrolling

Mosh provides the same core functionality as ET, but it does not support native scrolling or tmux control mode (tmux -CC). If your workflow depends on either, that is a deciding factor.

How to decide

  • Pick ET if you want a remote shell that automatically reconnects without interrupting the session, and you care about native scrolling or tmux -CC.
  • Pick ssh if you only need a basic remote terminal and can reconnect manually after an outage.
  • Pick autossh if automatic reconnection is enough and a new session per reconnect fits your workflow (for example, you don't mind re-attaching tmux).
  • Pick mosh if its core functionality matches your needs and you don't need native scrolling or tmux control mode.

Where to go next

The source points to install and usage instructions under "Download" and "Tutorial" on eternalterminal.dev, and explains the mechanism under "How it Works." If you are evaluating ET against your current setup, start with the Tutorial to confirm it fits your tmux and scrolling workflow before switching.