Runloop
VM-isolated Devboxes for coding agents, with blueprints, snapshots and suspend and resume.
| property | type | values | required | kind default | this component |
|---|---|---|---|---|---|
| accelerator | enum | none | gpu | asic | no | none | inherited |
| blueprint | boolean | — | no | false | inherited |
| concurrency | integer | — | no | — | ▸ 3 |
| fanoutStrategy | enum | none | push | pull | hybrid | no | none | inherited |
| fanoutThreshold | integer | — | no | — | inherited |
| idempotent | boolean | — | no | false | ▸ false |
| instances | integer | — | no | — | inherited |
| keepAliveSeconds | integer | — | no | 3600 | inherited |
| managed | boolean | — | no | false | ▸ true |
| rateControl | enum | none | fixed | aimd | no | none | inherited |
| schedule | string | — | no | — | inherited |
| snapshots | boolean | — | no | false | inherited |
| trigger | enum | queue | stream | schedule | batch | manual | yes | — | ▸ manual |
Every rule whose selector covers this component's kind or its category. Whether a rule fires depends on the design: its properties, its edges and its groups.
Pure push fan-out over a social graph is brutal at the tail: one post from an account with millions of followers becomes millions of cache writes. A follower threshold above which readers merge at read time bounds that write amplification.
- — all of these hold:
- — the node's `fanoutStrategy` is "push"
- — the node's `fanoutThreshold` has no value
- — the design contains a node of kind graph-database
One worker pool consuming several queues lets a slow or poisoned queue starve the others. That is precisely what the design's per-queue isolation requirement forbids.
- — all of these hold:
- — the node has more than 1 incoming edge from a queue
- — the design requirement `isolation.perQueue` is true
A stateful compute node pinned to exactly one availability zone disappears with that zone, and its state goes with it. Nodes inside a cell are exempt, because there the cell is deliberately single-zone and redundancy comes from the other cells.
- — all of these hold:
- — the node's `stateless` is false
- — the node sits inside exactly 1 availability-zone group
- — this does not hold:
- — the node sits inside at least one cell group
nodes:
- { id: "runloop", component: "runloop" }# yaml-language-server: $schema=../../schema/component.schema.json # Runloop: VM-isolated Devboxes where coding agents run tools, with blueprints, snapshots and suspend and resume. # Per "Your Runloop Trial", a new account gets 3 concurrent devboxes with a 1-hour keep-alive, sizes up to Medium, # 5 blueprints and 10 snapshots. schemaVersion: "1" type: "component" id: "runloop" kind: "worker" provider: "default" docs: "https://docs.runloop.ai/docs/overview/your-runloop-trial" aliases: ["Runloop Devboxes"] defaults: managed: true trigger: "manual" idempotent: false concurrency: 3 properties: keepAliveSeconds: type: "integer" default: 3600 blueprint: type: "boolean" default: false snapshots: type: "boolean" default: false