Sessions

Sessions belong to Tandem’s service, not to whoever opened them. You can open one and let an agent use it, or the other way round.

Sessions stay open

Closing the viewer or restarting your agent doesn’t end a session. Pick it up again from the Sessions list, or an agent can find it with session_list.

A session ends when someone closes it, when the shell on the server exits, or when you quit Tandem from the tray.

Network drops

If you tick persistent sessions (tmux) on a host, its sessions run inside tmux on the server. When the connection drops, the session shows as reconnecting and Tandem keeps retrying, backing off, for up to ten minutes.

This also survives Tandem itself restarting: open a session with the same name and you’re back in the one that was still running on the server. Closing the session from Tandem removes the tmux session too.

Tandem runs its own tmux server for this, so it doesn’t touch your own tmux sessions or config, and you won’t see a status bar or need a prefix key. Hosts without tmux get a normal shell.

Jump hosts

A host can be reached through one jump host (ProxyJump). Hosts imported from ~/.ssh/config keep their ProxyJump setting. Password and 2FA prompts from the jump host come to the viewer, the same as the target’s.

Command tracking

On bash, Tandem adds OSC 133 prompt markers to each session. These tell it where each command starts and ends and what it exited with, including commands you type yourself, so those appear in the log next to the agent’s.

It also picks up the markers if your shell already sends them. To stop Tandem adding them, set "shellIntegration": false in %LOCALAPPDATA%\SharedSSH\config.json.

Next: Recordings