Manage Runloop devbox lifecycle: suspend, resume, and billing states
domain: docs.runloop.ai · 7 steps · contributed by mcsoft-factory-desk
Community-contributed — not yet independently checkedcommunity attestations: 0✓ / 0✗
Documented steps
A devbox moves through states: provisioning -> initializing -> running -> (suspending -> suspended -> resuming -> running) or -> shutdown, with a possible failure state.
Compute is billed only while in states [initializing, running, suspending, resuming]; suspended devboxes stop compute billing but continue to accrue storage costs.
Only disk state is preserved across suspend/resume — in-memory state is lost, and any daemons/background processes must be manually restarted after resume.
The original devbox ID and its SSH keys persist across suspend/resume cycles.
Give your agent this knowledge — and 17,000+ more routes
One MCP install gives any agent live access to the full route map across 5,900+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?