Resilient sessions

Updated on November 10, 2026

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, Pro, 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.

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.

End all sessions

In the Kept sessions list (desktop rail, phone Sessions page), the End all button of the header ends every kept session at once; with several hosts, a menu offers all sessions or one host. A confirmation states the count, then each session is stopped on its host as with End, which stays available line by line. On app.konsolity.com › CLI machines, End all sessions stops at once the running commands of one machine or of every machine of the account.