Skip to content

Session Manager

Sessions are saved connections. Each one stores the host, port, username, auth method, and optionally a folder and tags. Instead of typing connection details every time, you save them once and connect with a click.

Reach supports three authentication methods:

  • Password - Just a username and password.
  • Private Key - Supports OpenSSH and PEM formats. Ed25519, RSA, and ECDSA keys all work. If your key has a passphrase, you’ll be prompted for it.
  • Agent - SSH agent forwarding. This one is planned but not implemented yet.

Click “New Session” in the sidebar. Fill in the host, port, username, and pick your auth method. Hit save. That’s it.

If you just need to connect once without saving anything, use Quick Connect instead. Type the host, port, and username, and you’re in.

Folders let you group sessions together. You can nest folders inside other folders. Drag sessions between folders to reorganize.

Tags are comma-separated labels you can add to any session. Use them for filtering when your session list gets long.

Click a session card to connect. If you have a saved password or key, it connects right away. If not, you’ll get a password prompt. There’s a “Remember password” checkbox that stores the password encrypted in the vault for next time.

Session credentials are encrypted at rest with XChaCha20-Poly1305. They live inside the vault, not in plaintext config files. You won’t find passwords sitting in a JSON file somewhere.

Duplicate lets you clone a session to quickly create a similar one. Handy when you have a bunch of servers with the same username and auth setup but different hostnames.

Session sharing lets you send sessions to teammates securely. It uses X25519 key exchange: you swap public keys, and the session data gets encrypted specifically for the recipient. Nobody else can read it, even if they intercept the payload.