Look at the machine of anyone who administers servers and a pattern appears. One program for shell sessions, another for the graphical desktop of a Windows machine, a third for the serial port on a switch or a development board. Each is good at its own thing, and each keeps its own list of hosts, its own credentials, its own idea of how a session should look.

WoTerm is built on the opposite assumption: that these are four views of one job. A remote shell, a Telnet session, a serial console and a remote desktop all live in the same window, with file transfer attached, on Windows, macOS, Linux and – unusually – Android. The source is open and the base version is free, with a paid tier on top for the heavier features.

Four protocols, one interface

The shell client handles password, key and interactive authentication, and reads the system's existing configuration file so sessions defined elsewhere appear without being retyped. The attached file browser speaks the file transfer protocol that runs over the same connection: drag to upload and download, edit a remote file in place, watch a file for changes and keep a local copy in step.

The remote desktop side scales the session intelligently rather than stretching it, and handles high resolution displays where the pixels are small enough that a naive scaling makes text unreadable. The serial console covers the baud rates and data bit settings that embedded work and network equipment still require, which is the part most modern terminal programs have quietly dropped.

Tabs, groups, and one command to many machines

Sessions open in tabs, which is ordinary. What is less ordinary is the grouping: servers can be organised into named sets, and a command typed once can be sent to every member of a set. For the change that has to be applied to thirty machines, this turns a repetitive and error-prone afternoon into a single action followed by reading the output.

The Android client is worth a mention for the same reason it is unexpected. It is not a replacement for a desk, but when a service stops at an awkward hour and the nearest computer is not near, a shell on the phone in your pocket is the difference between a fix and a wait.

Local ecosystem and account sync

The program pays explicit attention to the operating systems and processor architectures used in its home market, including several local Linux distributions and work on the open instruction set architecture and on domestic processor designs. That is not a detail for everyone, but for the organisations that need it, it is the deciding one.

A newer addition is an account system: connection definitions and preferences follow the account, so a replacement machine is configured by signing in rather than by rebuilding a list of hosts from memory.

Appearance and editions

Themes and colour schemes are customisable, and terminal font, cursor style and scrollback size are adjustable – small settings, but the ones that decide whether hours in front of a terminal are tolerable. The paid tier adds deeper cluster operations and more elaborate connection management, while the free base version covers the daily work.

An honest kind of integration

It does not try to beat the specialist tools at any single protocol. It tries to remove the need to keep three of them open, and for the ordinary run of administrative work that is the more useful ambition.