
How it works
Each Omnara machine is one boxd machine in your org. Between turns the Omnara daemon goes idle, and boxd puts the machine on standby once its network goes quiet. Memory, processes, and open sockets are kept on standby. When the agent needs the machine again, Omnara wakes it through the boxd API and the daemon is back online in 0.6 to 1.2 seconds. Machines come in boxd’s four sizes: 1 vCPU / 4 GiB, 2 vCPU / 8 GiB, 4 vCPU / 16 GiB, and 8 vCPU / 32 GiB. Save your tools in a snapshot and every new machine is created from it.Set up a boxd pool
Create an API key fenced to the org your machines should run in, and store it as an Omnara org secret:sleep_after_ms idles the daemon after a minute of inactivity, which lets boxd put the machine on standby:
boxd snapshots save <machine> <name> and pass "snapshot": "<name>" in the provider options. A machine created from a snapshot keeps the size of its source machine, so a configured size has to match it.
Omnara’s machine pool docs and self-hosting configuration cover the rest, including startup_script, auto_suspend_secs, and runtime protection.