Six jobs you could automate today
Each is a trigger, a prompt and the choices about who runs it.
- A pipeline fails: an agent reads the log, fixes the build and leaves the change on its branch
- A webhook fires on a new issue: an agent reproduces it, labels it and proposes the change
- A nightly schedule: a dependency audit, filed as a chore
- A weekly schedule: release notes drafted from what landed
- A Discord message mentions the agent: it answers with the repository open
- A Visitor chat visitor asks: an agent answers, and holds what it should not answer alone
Control what starts and what it can do
Each run uses the identity, model, permissions and limits you set. An optional check command can skip the run before it uses any tokens.
- Wake on a GitHub push, a Sentry alert, a Stripe payment, inbound email, a Discord message, or cron
- The check is your own code. It decides whether a specific event needs an agent
See every automated run on the board
An automatically started agent appears like any other, with its own card, diff and review.
acme-shop · /agents
One run can wake the next
Work hands down a chain: triage wakes the fixer, the fixer wakes the reviewer.