Skip to content
Spinbox is experimental: APIs change and data may be lost. Status lists what is built and what proves it.

spin ssh-config

View Markdown
Write ~/.spin/ssh/config and include it from ~/.ssh/config, so any program that runs ssh
reaches a workspace as the host spin.<workspace>: ssh, scp, rsync, VS Code's Remote-SSH.
Each connection gets a fresh five-minute certificate for your key, and is carried through
the platform like 'spin ssh'. A workspace has to be running: a start under way is waited for.
The block asks for the one key exchange a workspace accepts, mlkem768x25519-sha256, which
OpenSSH has from 9.9. An older ssh refuses the whole of ~/.ssh/config over it, for every host,
so nothing is written for one.
Examples:
spin ssh-config
ssh spin.my-workspace
rsync -a ./src/ spin.my-workspace:/root/src/
Usage:
spin ssh-config [flags]
Flags:
-h, --help[=true|false] help for ssh-config
-i, --identity string Identity file (private key); default: the first key this machine holds that your keyring lists
Global Flags:
--config string config file (default is $HOME/.spin/config.yaml)
-o, --output string text for a person, or json: one document of what the API answered, and no prose (default "text")
--profile string named profile to use; SPIN_PROFILE names it when this flag does not (default "default")
--traceparent string the W3C traceparent of the span this command is part of; its own span is sent to the installation unless the profile says telemetry: false

Generated by task reference from spin/cmd/cli at 51f7e0dea.

Installations run Spinbox v20261027.01; the reference is generated from spin v20261114.01 (51f7e0dea). This page as Markdown, for a model or a terminal.