An automation runs an agent against your repositories on a schedule, or when agents keep reporting the same friction, without anyone present. Use it for recurring maintenance or any goal you want chipped away at over time. This guide sets one up.
Create the automation
Choose New automation and fill in:
- Trigger — Schedule, or Friction reports when friction is enabled.
- Name (and an optional Description).
- Instructions — the prompt the agent runs each time (scheduled automations; a friction run’s instructions are the friction item’s report).
- Repositories — one or more. Each run checks out all of them; with a single repository you can also pick a base branch.
- Blueprint — the workflow to follow — and an optional Model.
- Environment variables and Secrets if the run needs them.
Choose a trigger
Schedule runs the automation at set times. Add one or more schedules. For each, pick a type — Hourly, Daily, or Monthly — set the time (hour and minute for daily; day-of-month for monthly), and choose a timezone. You can add several schedules to one automation.
Friction reports (when friction is enabled) runs the automation when an open or routed friction item in one of its repositories reaches the number of reports you set. The run works in that item’s repository with the item’s report as its instructions, and moves the item to Fixing. Each item runs an automation at most once, and items already past the count when you turn the automation on don’t run.
Run it
Save the automation. It will run at the next scheduled time — or choose Trigger now to run it immediately. Use Pause / Enable to turn the schedule off and on; the automation shows its next run (or Paused).
Review the runs
Each run appears in the automation’s run history. Every run is a task/implementation: it follows the blueprint’s steps in a sandbox and opens a pull request you review — see Review implementations.