Skip to main content
Use sandbox environment configuration to set size, lifetime, environment values, metadata, and credentials when you create a machine. A template supplies the starting image; each machine has its own configuration.

​
Set size and kind

--timeout belongs to temporary machines. --idle-timeout belongs to persistent machines. See machine lifetime.

​
Set environment and metadata

The create API accepts envVars and metadata maps. Save this as create.json:
Use metadata to describe the machine. Plain environment values can persist in files and captured process memory. Supply AI credentials through a profile and keep secrets out of reusable build inputs.

​
Attach a credential profile

The CLI selects the saved profile through metadata["bead.credentialProfile"]. MCP create also accepts a profile UUID. You can select a profile for a later runner prompt. OpenClaw and Hermes copy credentials once into native app storage and own subscription refresh after creation. Vault edits affect new app machines. See credentials.

​
Choose retained state

Use a ready snapshot as templateID to restore prepared memory. It must keep its original CPU and memory size. For a different size, use a disk template to start a new machine. Temporary machines can attach a supported persistent volume with volumeMounts.