Skip to main content
Use nullspace machine create to boot a machine from a template or reusable snapshot. The command returns the machine ID and connection metadata.

Create From A Template

Pass --json when you want the full response:

Use A Template Warm Pool

Pass --warm-pool when a machine should try to claim ready capacity from a template warm pool:
Use --warm-pool-mode require for latency-sensitive work that should fail with warm_pool_unavailable instead of cold creating when no matching ready instance is available. Use --warm-pool-mode bypass to force a cold create.

Working Directory, Environment, And Metadata

The default mutable workspace for repo-style flows is /workspace, but commands and file APIs can use other absolute paths inside the machine.

Timeouts And Auto-Resume

Timeout actions control what happens when a machine idles. Prefer --on-timeout pause at create time when the machine should hibernate instead of being destroyed, especially with --auto-resume. The lower-level --timeout-action hibernate flag maps directly to the API timeout_action field; use it only when you intentionally need that raw field. For an existing machine, use nullspace machine timeout set ... --action hibernate.

Create From A Snapshot

Snapshots are reusable baselines. They are different from fork, which branches a running machine immediately.

Attach Volumes

Use volumes when multiple machines need durable shared files.

Networking And Desktop Options

allow_out entries are CIDR ranges. Desktop create options are only valid for desktop templates.

Idempotent Retries

Use an idempotency key when retrying a create request from automation.