Resilient sessions
The tab and the transport
A Konsolity tab is separate from its SSH connection. When the network drops (Wi-Fi off, sleep, switch to 4G), the tab stays with its buffer and the signal line goes Offline, automatic resume, then Reconnecting, attempt n. Nothing to retype.
Persistence
On a server that has tmux (or screen), Konsolity creates the session in a multiplexer on a dedicated socket (konsolity) and reattaches it on every reconnection. Set per host: automatic, tmux, screen, none. Without a multiplexer the session is “not resumable”: a banner says so.
Konsolity bundles tmux on macOS and Linux: on a computer of the account that lacks it, it is used automatically.
Close, keep, terminate
Closing a tab does not kill the session: it goes to Kept sessions and resumes in one click. Terminate is explicit and kills the session on the server.
Resume on another device
With an account (Cloud, Studio, trial), a session open on the Mac appears on the iPad under “On your other devices”: Resume here reattaches the same tmux session. The marker next to the host in the Parc counts the sessions open here and elsewhere.
Several sessions per host
Right click on the host, on the rail entry, or tab ⋯ menu › New session on this host.
Links
From a session, Link other hosts of the vault: ssh web-01 then works straight on the server, through an ephemeral SSH agent. Everything is revoked on close.