Concept · not yet built
The engine runs anywhere. Something has to watch it.
The control plane for unattended Engine runs — provisioning sandboxes, scheduling sessions, and supervising a fleet of cloud agents so a run doesn't need a laptop open to finish. Concept stage.
provision
Spin up a sandbox, clone the target repo, hand it an engine session.
schedule
Queue runs, stagger them across a fleet, respect a budget ceiling.
supervise
Watch the event stream, restart what dies, page you when it can't.
settle
Merge, PR, keep, or discard — routed back to you, not decided for you.
Why it's separate from the engine.
The engine already refuses to guess about anything that mutates git — settle is always your call, and a run degrades cleanly with no key, no model, no judge. The cloud controller doesn't get to relax that; it just gives that same discipline a fleet to run in, instead of one laptop with a terminal open.