Documentation

Connect with SSH, scp, sftp and rsync

Coming soon. Standard SSH access and editor connections are not available yet.

Connect when enabled

On macOS or Linux, install rzv and OpenSSH, sign in with rzv login and select your workspace. The sandbox must be running, and Runzivo must have SSH turned on for your environment. SSH from a Windows computer is not supported yet. Use rzv sandboxes exec instead. Connecting needs sandboxes:write. Generating configuration with an API key needs sandboxes:read. No public IP or public SSH port is needed.

Commands after enablement. Replace <sandbox-id>

rzv sandboxes ssh <sandbox-id>
rzv sandboxes ssh <sandbox-id> -- 'uname -a'
rzv sandboxes ssh-config <sandbox-id> --write
ssh <sandbox-id>.rzv
scp file.txt <sandbox-id>.rzv:/workspace/
sftp <sandbox-id>.rzv
rsync -a -e ssh ./project/ <sandbox-id>.rzv:/workspace/project/
ssh -N -L 8080:localhost:3000 <sandbox-id>.rzv

Use VS Code or Cursor

Run ssh-config with --write as above. It maintains its own Host block and adds an Include to ~/.ssh/config, preserving other configuration. Confirm plain ssh works, then install your editor’s Remote SSH extension, choose <sandbox-id>.rzv and open /workspace. The generated ProxyCommand uses rzv sandboxes ssh <sandbox-id> --stdio. Preserve host verification. We have not yet tested VS Code or Cursor against a live sandbox.

Transfer files

Use the generated SSH alias with scp, sftp or rsync. Review files before copying: source folders often contain credentials. Do not disable host-key checks or paste tokens into commands.

Use rzv sandboxes terminal <sandbox-id> for the existing PTY shell. Only rzv sandboxes ssh <sandbox-id> with no extra arguments can fall back to that shell when SSH or OpenSSH is unavailable. Remote commands and file transfers receive guidance instead.

Forwarding and limits

Local port forwarding reaches only services on the sandbox’s own localhost. Remote forwarding, SSH agent forwarding, X11, tunnels and Unix-socket forwarding are disabled. At most two SSH sessions run per sandbox. Sessions close after thirty idle minutes or when the sandbox stops, expires or is deleted.

Use case: review an agent’s work

Once enabled, connect from VS Code or Cursor, let your coding agent edit files in the sandbox and inspect the diff before you commit. Forward a local preview port to a service listening on the sandbox’s localhost. Copy work out before the eight-hour sandbox lifetime ends.

Language

Français (Canada)