Tempest Remote — SSH, SCP & rsync
The Tempest Remote Editors launcher can keep an SSH alias alive for ordinary command-line tools. It uses the Remote SDK.
Download and extract the launcher, install Node.js, then run:
node scripts/remote.js connect --server ubuntu-cloudnetKeep it running. Copy the returned sshHost into a second terminal, replacing this example:
ssh tempest-example-123456789abc
scp -O ./file.txt tempest-example-123456789abc:/tmp/
rsync -av -e ssh ./project/ tempest-example-123456789abc:/tmp/project/scp -O selects legacy SCP mode because the relay does not currently expose SFTP subsystem requests. The remote host needs the corresponding scp/rsync executable. Each command opens its own SSH channel; the keepalive does not carry terminal input.
Ctrl+C stops the launcher and releases its attachment. Other attached clients may remain connected. An expired alias needs connect to be run again. Existing user SSH configuration is preserved.
Requirements
Install Tempest CLI, sign in with tempest login, and save your SSH servers in Tempest. The CLI must provide tempest remote control and tempest remote pipe. OpenSSH must be available locally and the vault must allow TCP forwarding. Accounts, authentication, jump hosts and proxies stay in Tempest CLI.
Existing managed connections keep their original SSH alias. New connections receive a human-readable name. Use the returned alias rather than deriving one from a server name or ID.
See also
Last updated