# spin ssh-config

**Spinbox is experimental: APIs change and data may be lost.** What is built and what proves it is on [Status](https://docs.spinbox.dev/reference/status.md); what Spinbox does not do is on [Limitations](https://docs.spinbox.dev/overview/limitations.md).

> spin ssh-config: Make every workspace reachable with plain ssh, as the host spin.<workspace>.

<!-- Generated by tools/refgen from spin:cmd/cli. Edit the source, not this file. -->

```
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
```
