SSH and VS Code Remote

SSH uses your own public key and strict host-key verification. Add the public key through the SSH-key API or cec ssh-keys add; never upload the private key. Attach the key when creating a computer or through the supported key configuration.

Configure the connection

GET /computers/{id}/ssh supplies the jump connection and host-key fingerprints. cec ssh-config <id> emits the actual SSH configuration; save it to your own chosen file and retain the corresponding known_hosts entries. Check the returned host fingerprint through the authenticated API before trusting a first connection. Keep StrictHostKeyChecking enabled.

The jump-host form uses ProxyJump and your key for end-to-end SSH authentication. Where the local network allows only HTTPS, cec ssh supplies the port-443 tunnel and can be used as ProxyCommand. It uses the exec access-token header; browser query-token exchanges do not apply. See SSH and SSH streaming.

VS Code and Cursor

Point the editor's Remote-SSH extension at the saved SSH config and select that host. The extension runs inside your computer after SSH succeeds; CE does not need your editor account credentials. Upload source with SSH/SCP or rsync, and keep exported files outside this server.

After restore or failure

A restore can change guest state, including SSH host-key files. On a mismatch, stop the connection and compare the new authenticated fingerprint with the expected restore outcome. Do not solve it by disabling host-key checking. SSH can remain usable when the in-guest agent is unavailable; check the computer state and key authorization independently of data-API readiness.

Dory is in development; these pages describe the planned service and may change. Questions: support@computeengines.com.