Automations: an agent on a schedule, a pull request or a push, across every repository you choose
Team → Auditor has an Automations tab. An automation is a trigger (a schedule, a pull request opened, made ready, pushed or labeled, or a push to a branch), an instruction in your words, a scope (every repository, a name pattern such as acme/*-theme, or a list), a permission (read, propose a pull request, or push) and what it may post: a comment, an issue or a pull request. One firing runs once per repository in scope, and a repository can opt out or replace the instruction from its settings drawer.
Every run is a conversation you can watch: the agent's steps appear as it works, a note you send reaches it before its next step, Stop makes it answer with what it has, and once it has answered you can reply to continue on the same commit with its edits still in place. Dry run shows what each repository would get without writing anything to GitHub.
Start from a blank automation or a recipe: triage failed GitHub Actions, fix CI failures, triage Linear or Jira issues, find vulnerabilities, flaky tests, and eight more. Each run is billed as inference to the team's Auditor key like a review, with a per-run budget, an optional monthly budget per automation and the team's spend cap on top; one live run per repository and subject, 20 runs an hour per repository, and a big fan-out goes through the queue at eight repositories a minute.
Propose and Push need the GitHub App's write permission; an installation made before it existed approves the updated permissions in GitHub. Automations is in beta.
More in Automations.