Skip to main content
Automations let Operator run recurring work on a schedule. They are platform level tasks, not scoped to a single instance.

​
What automations are for

Agent evaluation

Check whether predictions have resolved, score agents against outcomes, trigger the next evolution generation.

Fleet operations

Health checks across instances, maintenance restarts, daily activity summaries, cross instance coordination.

​
How automations work

Each automation stores:
FieldDescription
NameHuman readable label
PromptWhat the Operator agent should do when the automation fires
Cron5 field cron expression
TimezoneDefaults to UTC
StateEnabled or disabled
When an automation runs, the Operator agent executes the prompt with full tool access: inspecting instances, running test inputs, scoring results, changing config, granting secrets, or messaging agents.

​
Cron format

minute hour day-of-month month day-of-week
ScheduleCron
Every hour0 * * * *
Every 6 hours0 */6 * * *
Daily at 9 AM0 9 * * *
Weekdays at 9 AM0 9 * * 1-5

​
Example prompts

Check whether yesterday's AQI predictions have resolved.
Pull actual AQI readings for all 50 cities.
Score each agent variant against reality.
If a new generation is warranted, run one.
Post a summary of score changes.

Agents

The evolution loop that automations can drive

Webhooks

Event driven triggers instead of schedules

Instances

What automations operate on

API

Create automations programmatically