Sessions

Multi-session SSH and projects

SSHaven keeps an SSH connection pool so you can leave remote work running, attach to tmux sessions as tabs, and tag agents with projects that span more than one machine.

A pool, not a single disposable shell

Classic mobile SSH apps often treat a connection as one screen: connect, type, disconnect. That fights how people actually work with agents — several tmux sessions, more than one host, and a job you do not want killed when you switch apps.

SSHaven’s pool keeps sessions you can return to. Leave a tab without tearing down the remote process. Open a classic shell when you just need a prompt.

tmux as tabs

On each server you can browse remote tmux sessions — name, cwd, activity, a pane preview — and attach as tabs. Create or kill detached sessions from the phone. One live interactive PTY is attached at a time in the workspace; inactive tabs keep a capture preview.

That is the control plane for the agent pilot board: the fleet is tmux, not a proprietary cloud runtime.

Projects across servers

Tag sessions with project names that are allowed to span machines. Browse the fleet by Server, Project, or agent type. Friendly agent names keep “API rewrite on prod-eu” distinct from “docs on the lab Pi.”

Project and session labels are stored on your device, not in an SSHaven cloud profile.

What stays running when you leave

  • Remote tmux sessions keep running on the server you started them on.
  • The phone can disconnect and come back; the remote job is not your app’s process.
  • Notifications can still tell you when a tracked agent needs you — so you reopen the right tab instead of guessing.

More about SSHaven