desk machine
Use desk machine to provision a native Linux host on Vultr, register an existing SSH host, and connect to saved machines.
A driver provisions or registers a machine. A runtime determines how an agent runs on it. These commands prepare a native host; Docker is not required. SSH connects to the host. Existing hosts use the generic driver without giving Desk responsibility for their cloud lifecycle.
Machines and runtimes
Section titled “Machines and runtimes”| Concept | Purpose | Example |
|---|---|---|
| Harness | The agent that runs your work | Claude, Codex, Qoder, Bob |
| Runtime | How the agent runs | Native; container support is planned |
| Driver | How the machine is provisioned or registered | vultr, generic |
| Machine | Where the work runs | Your local machine or a named cloud host |
| Transport | How Desk connects | SSH |
Native execution uses the selected machine’s normal user environment and agent login. The planned remote move workflow will default to native execution. Runtime selection and remote move flags are not available yet.
Subcommands
Section titled “Subcommands”| Command | Purpose |
|---|---|
| desk machine create | Provision a Vultr machine or resume its creation |
| desk machine ls | List saved machines |
| desk machine add | Register an existing SSH host |
| desk machine check | Check connectivity and native host tools |
| desk machine connect | Open an SSH shell; alias: ssh |
Machine records live at ${DESK_HOME:-$HOME/.desk}/store/machines/NAME.json. local is reserved for the current machine.
Next: move work to the machine
Section titled “Next: move work to the machine”Remote pack transfer and desk move --machine=devbox are planned separately. Current move commands still launch local agents. Machine provisioning and SSH connection are the foundation for that next step.