SSH and SFTP
SSH is built in, not bolted on: hosts live in an encrypted vault, connections support jump hosts and port forwards, and every SSH session carries its files with it.
Adding a host
Open the SSH connections screen (the drawer, or Ctrl+K and
type ssh) and add a host. Choose how to authenticate: your SSH agent, a
password, or a key file. Add jump hosts and port forwards on the same
profile if you need them.
Saved hosts are sealed in a local vault, encrypted at rest with a machine-local key. Nothing about a host leaves your machine unless you turn on connection sync.
Importing existing hosts
Hosts in ~/.ssh/config are not imported automatically -
the connections screen offers an explicit import instead, so you decide
what enters the vault.
Files over SFTP, and past it
On any SSH session opened from the vault, the files button opens an SFTP browser for that host: browse, upload, and download without leaving the session. That is the start of the file story, not the end of it. The same directory shows beside the live terminal in the web dashboard and on the phone, and a file dropped on a pane rides the shell's own bytes to wherever the pane reaches, jump hosts and containers included, where SFTP cannot follow. All of it is on Moving files.
Vaults
Connections organize into named vaults - Personal, Production, one per client. Locally they group your hosts; with a paid plan they sync across your machines, and on a Team plan a vault can be shared with teammates, wrapped to each member's own key (how that works).
When the machine is yours, skip the jump host
SSH needs a path into the target, which is what bastions and jump chains are for. For machines you control, there is a simpler shape: install the headless daemon and the box dials out to the relay instead - no inbound port, no jump host, reachable from your phone even behind NAT or a VPN. From a session there, SSH onward to anything the machine can see.