Skip to main content
Runloop Devboxes are managed, isolated Linux sandbox environments for AI coding agents that can run, suspend, resume and shut down. The following table shows what CostGraph runs on this provider.

​
Connect

Run the dispatcher with provider set to runloop and these variables:
  • RUNLOOP_API_KEY
For CI runners, CostGraph picks the smallest Runloop size class that fits. providerTemplate takes a blueprint (bpt_...) or snapshot (snp_...) id. If you connected Runloop for cost data, CostGraph’s dispatcher can start sandboxes with the key from your Runloop integration. That key then needs the permissions in the next section as well.

​
Key and permissions

RUNLOOP_API_KEY is a Runloop API key, created only in the Runloop dashboard (secret shown once, optional expiry). Secret keys are ak_…, restricted keys rk_… Use a restricted key (rk_): per resource type None/Read/Write, unconfigured types default to None, scopes not editable after creation. Minimum: Devboxes = Write (Blueprints/Snapshots = Read only if launching from them). Secret keys (ak_) grant full account access. Sources: docs.runloop.ai: dashboard, docs.runloop.ai: start stop, docs.runloop.ai: your runloop trial, docs.runloop.ai: sizes, docs.runloop.ai: devbox architecture.

​
Limits

  • Default devbox lifetime 1 hour, configurable at create via keep_alive_time_seconds (no maximum stated); idle policy is opt-in (lifecycle.after_idle, suspend or shutdown); use one or the other, not both. (source)
  • Pro Trial: 3 concurrent running devboxes, X Small/Small/Medium only, max keep-alive 1 hour. (source)
  • Sizes up to XX_LARGE 8 vCPU/32 GB; CUSTOM_SIZE up to 16 vCPU, 64 GiB RAM, 64 GiB disk. (source)
  • Architectures x86_64 (default) and arm64; blueprints must match the devbox architecture. (source)