Mosh vs Et

Published
Length
3 min read

Luis Felipe Dias

All posts

The mosh vs et choice comes down to how your remote shell handles bad networks. Teams pick Mosh for fast local typing and Eternal Terminal for native scrollback. Standard SSH drops your work when your laptop sleeps or changes Wi-Fi networks. Both Mosh and Eternal Terminal fix this problem for remote engineers. They keep your shell alive across network changes and long drops. Yet they use very different network models to reach this goal. Core architecture in mosh vs et Mosh stands for mobile

Your coding agents run with your access.

Claude Code reaches prod with a developer's credentials, and approval prompts get clicked through. hoop.dev checks every query, masks sensitive data, and holds risky changes for a human.

The mosh vs et choice comes down to how your remote shell handles bad networks. Teams pick Mosh for fast local typing and Eternal Terminal for native scrollback.

Standard SSH drops your work when your laptop sleeps or changes Wi-Fi networks. Both Mosh and Eternal Terminal fix this problem for remote engineers. They keep your shell alive across network changes and long drops. Yet they use very different network models to reach this goal.

Core architecture in mosh vs et

Mosh stands for mobile shell and runs over UDP after an initial SSH login. It does not send a raw stream of text across the wire. Instead, Mosh keeps a copy of the screen state on both sides. The client and server sync only the screen changes over UDP. Mosh also predicts your keystrokes and shows them right away on screen. This makes typing feel instant even on slow cell networks or train Wi-Fi.

Eternal Terminal, often called et, takes a different path over TCP. It uses SSH for the first login and then starts a persistent TCP session. Unlike Mosh, Eternal Terminal sends a true stream of bytes to your terminal. Because it sends raw output, your local terminal app keeps its normal scrollback buffer. It also supports native tmux control mode so you can manage windows with ease.

Tradeoffs in scrollback, ports, and firewalls

Screen sync gives Mosh great speed, but it breaks standard terminal scrollback. When text leaves the visible screen in Mosh, you cannot scroll up to read it. Most engineers run a terminal multiplexer like tmux inside Mosh to get scrollback again. Mosh also needs open UDP ports on the remote host to work. Strict corporate firewalls or cloud load balancers often block UDP traffic.

Eternal Terminal avoids the scrollback issue because it streams every line of text. If a command dumps thousands of lines, Eternal Terminal sends all of them. On a slow link, you might wait while that text catches up after reconnecting. On the network side, Eternal Terminal needs a dedicated TCP port open on the server. Many network teams prefer allowing one TCP port over a wide UDP port range.

K8s RBAC Role vs ClusterRole: architecture patterns and best practices

Continue reading? Get the full guide.

Free. No spam. Unsubscribe anytime.

How teams choose between the two tools

Pick Mosh if you work on high-latency links like planes or weak cell signals. Local echo makes editing files and running shell commands much less painful. You will just need to pair it with tmux for history and extra tabs.

Pick Eternal Terminal if you want your local terminal app to behave as normal. It fits well when you need mouse scroll, native copy and paste, and TCP rules. Both tools need a binary installed on the client and the remote server. Neither tool replaces your core security controls, user keys, or audit logs. Teams still need a clear way to manage who can log in to hosts.

Govern statements and responses across databases and APIs

Good config and scoped roles are needed setup. They do not check single queries in flight or mask sensitive fields in returned rows. Across Postgres, MySQL, SQL Server, MongoDB, ClickHouse, Kubernetes APIs, SSH, and internal HTTP endpoints, hoop.dev runs beside each supported service as an open-source proxy, a sidecar for your database or API.

First, hoop.dev guardrails block banned queries before they run. Then hoop.dev data masking rewrites matched sensitive values in responses in memory. The audit trail records every statement and verdict per resource. Furthermore, hoop.dev holds SOC 2 Type II and is open source on GitHub.

Frequently asked questions

Does Mosh or Eternal Terminal replace SSH?

No, both tools use standard SSH to log you in and check your keys first. After the login step finishes, they switch over to their own session daemon.

Why does scrollback break when I use Mosh?

Mosh only syncs the current visible screen state to save bandwidth on bad links. You can run tmux or screen inside your Mosh session to keep full scroll history.

Which tool works better behind strict firewalls?

Eternal Terminal is often easier to run through strict network firewalls because it uses TCP. Many office networks and cloud tools block the UDP ports that Mosh needs.

The query runs. The emails stay hidden.