A master enabled flag plus four per-capability switches. Turning the master off makes every cron pass return 'skipped: autonomy is switched off' on its next tick. The per-capability switches exist so imagery can be paused — for instance while image credits are out — while the audit loop and the publisher keep running.
Also called: kill switch · stop everything · pause automation · master switch
- 1Every autonomous route opens an AutonomyRun and returns early when config.enabled is false.
- 2allowed(cap) requires both the master switch and the named capability switch.
- 3The panel's 'Stop everything' button writes the flag through setAutonomy, taking effect on the next cron tick.
- 4The capability checkboxes are disabled in the UI while the master switch is off, so the state is never ambiguous.
- 5The weekly audit email leads with 'Autonomy is switched off' when it is, and reframes everything below as a proposal.
The per-capability split has a stated reason: "Per-capability switches, so imagery can be paused without stopping the audit loop (e.g. while kie.ai credits are out)." Without that, a single failing dependency would force the whole system off, and a system people turn off entirely does not get turned back on.
- There was no way to stop autonomous work without shipping code.
- One failing capability forced the entire system off.
See it on your own jobs
Twenty minutes, your numbers, no slide deck. We’ll build one of your real buildings in front of you and send you the estimate link at the end — yours to keep either way.
or keep browsing features →