CLI
Session lifetime
Once connected, the session closes after 30 minutes without SSH activity or after 12 hours total, whichever comes first. Activity is defined as any SSH traffic in either direction. SSH session lifetime is independent of the machine’s lifecycle. If a machine sleeps during an active SSH session, that session will close. If a machine is configured with autosleep, the SSH session is treated as active work. The machine will not autosleep until the session closes, even if no other activity occurs on the machine.Connect from the SDK
Use the SDK when your application needs to control the SSH connection itself. Generate an ephemeral key pair, keep the private key in your application, and pass the OpenSSH-formatted public key to the SDK.connection.user_certificate as the OpenSSH CertificateFile. Write connection.host_trust to UserKnownHostsFile as an @cert-authority entry, using its host_pattern and public_key. Then connect to connection.endpoint on connection.port as connection.ssh_username, using the private key that matches the public key you submitted.
Set IdentitiesOnly=yes, GlobalKnownHostsFile=/dev/null, and StrictHostKeyChecking=yes so OpenSSH uses only the temporary identity and Dedalus host authority. Delete the private key, certificate, and host-trust files when the connection closes.
