~/.ssh/config. The Boat CLI does not write that file. Use the script below to write one entry per sandbox.
Before you start
- An API key with the
sshaction inBOAT_API_KEY. Read API keys. - An SSH key pair at
~/.ssh/id_ed25519. Create one withssh-keygen -t ed25519if you have none. curlandjq.- On Windows, run the script in Git Bash. VS Code reads the same
C:\Users\<you>\.ssh\config.
1. Save the script
Save this asboat-ssh-config.sh:
boat-ssh-config.sh
2. Include the entries in your SSH config
Add this line at the top of~/.ssh/config, before any Host line:
~/.ssh/config
3. Write the entry and connect
- VS Code: install the Remote - SSH extension. Run Remote-SSH: Connect to Host… and pick
bx_f7k2q9hd. - Cursor: run Remote-SSH: Connect to Host… and pick
bx_f7k2q9hd. - Other tools that read
~/.ssh/configwork the same way.
/home/user/<your-repo>.
After a resume or a fork
- Run
bash boat-ssh-config.sh <id>again. It writes the new address and the new host key. - Reconnect the editor.
REMOTE HOST IDENTIFICATION HAS CHANGED or cannot connect. Do not delete the key check. Run the script.
Good to know
- An open editor does not delay auto-stop. To keep the sandbox up for a work day, run
boat extend <id> --hours 8. Read Auto-stop. - The editor installs its server in
/home/user/.vscode-serveror a similar folder. Snapshots keep it, so the next connection after a resume is faster. - Your key stays authorized after a stop, a resume and a fork. The script authorizes it again anyway. This is safe.
boat ssh <id>needs none of this. It finds the address and the host key itself.