Overview
When working with AI-generated code, you may need to debug the state of the project after the AI has run various commands. SSH allows you to connect your computer directly to a Devbox, enabling you to debug, run remote commands, and view or modify the remote filesystem. Runloop uses a transparent proxy to facilitate routing for all SSH access. Your SSH connection is end-to-end encrypted using standard SSH public key cryptography. The Runloop API provides a mechanism for retrieving SSH keys using a Runloop API key.Setup
We recommend using therl
CLI to interact with Devboxes. You can find installation instructions at https://github.com/runloopai/rl-cli.
Create and SSH into a Devbox
1
Export your API key
2
Create an empty Devbox
3
SSH into the Devbox
SSH into an You should now have a shell into the Devbox:
active
Devbox using the returned id
:4
Exit the SSH session
Type
exit
to leave the SSH session.5
Shut down the Devbox
When you’re done, shut down the Devbox:
Using VSCode with SSH
You can use SSH access to connect VSCode to the remote Devbox.1
Install VSCode SSH extension
Install the Visual Studio Code Remote - SSH extension.
2
Create a Devbox
3
Generate SSH config entry
4
Append to SSH config file
5
Verify the configuration
user
.6
Connect VSCode to your Devbox
You now have a ready-to-use SSH connection to the Devbox. Follow the remaining instructions in the VSCode SSH documentation to connect VSCode to your Devbox.
Security Notes
- All SSH connections are routed through Runloop’s transparent proxy.
- Connections are end-to-end encrypted using SSH public key cryptography.
- SSH keys are generated and managed securely through the Runloop API.