An automation is a configured, autonomous workflow bound to a repository and a blueprint (a workflow template). It runs on a schedule — no one needs to be present — and each run spawns a task/implementation that works toward the goal you defined and opens a pull request.
Use automations for ongoing, background improvement: recurring maintenance, sweeping fixes, or any goal you want the agent to keep chipping away at between sessions.
Creating an automation
When you create an automation you provide:
- Name and an optional Description.
- Instructions — the prompt the agent executes each run.
- Repository and an optional base branch.
- Blueprint — the workflow the run follows, and an optional Model.
- Environment variables and Secrets — plain key-value pairs and references to workspace secrets, passed to the sandbox at run time.
Schedules
An automation can have one or more schedules. Each schedule has a type — Hourly, Daily, or Monthly — plus the relevant time fields (hour and minute for daily, and day-of-month for monthly) and a timezone. The automation shows its next run time, or Paused when disabled.
Running & managing
From an automation’s page you can:
- Trigger now — run it immediately without waiting for the schedule.
- Pause / Enable — turn the schedule off or on.
- Edit its configuration or Delete it.
- Review its run history — the most recent runs, each a task you can open.
See the Create & run an automation guide for a walkthrough.