Persistence
Persistent machines
Save the runtime, model, memory selection, environment, and schedules as a Worker configuration. The control plane tracks its machine and lifecycle operations. Files and runtime state persist according to the selected provider; keeping a record is not an uptime or backup guarantee.
- runtime root
- logs
- cron
- artifacts
- saved configuration → runtime + model
- memory → persona + instructions + context
- compute → selected provider
- workspace → files + native history
- lifecycle → observed operation status
Capabilities
What you can use.
- Runtime root
- ~/.agent-machines
- disk-backed state
- Provider lanes
- 4
- E2B, Sprites, Daytona, Vercel
- Surfaces
- 7
- chat, terminal, logs, usage, cron, loadout, files
Workflow
From setup to result.
Configure
Choose a runtime and model, then edit its memory and abilities.
Run
Choose a credentialed provider and inspect the launch operation.
Continue
Return to saved files and supported native history; check the provider's persistence limits.