Automations: agents get to work when something happens
Noticing that CI broke or a PR got a comment, then handing it to an agent, is always left to you. Automations tie an event to a job: when a rule fires, an agent works in its own worktree following a playbook and delivers the result the way you chose.
This feature is in the Pro and Team plans. On the free plan it shows as locked; sign in with your AgentVera account and upgrade to unlock it. Compare plans
Events
Rules live in the project’s Details → Otomasyon → Otomasyonlar tab; the Çalıştırmalar (runs) view shows each rule’s history.
- CI went red: a run breaks in GitHub Actions, GitLab CI or Jenkins as connected in the CI/CD tab. Limit it with branch patterns such as “main, release/*”.
- PR comment: only comments from repo owners, members and collaborators count, never bots. If an agent is already working on that PR, new comments go to it.
- Issue labelled: the default label is “ajan”. The label has to come from a person with write access.
- Scheduled: a 5-field cron expression in local time, for example weekdays at 09:00.
The job and how it lands
When a rule fires, a Claude Code or Codex agent opens in its own worktree on an ajan/… branch and follows the playbook you picked. A rule can also start a flow from its Start node or prepare a Parallel team plan that waits for your approval. The landing setting decides where the result goes.
- Automatic: pushes back to the branch whose CI broke or to the PR’s branch, otherwise opens a PR; it never pushes straight to the default branch.
- Open a PR, push to the same branch, add to the merge queue, or leave it on the branch.
- While a project has no rules, four ready-made ones are offered: fix CI when it breaks, handle PR comments, do issues labelled “ajan”, update dependencies on Mondays.
Playbooks
A playbook is the instruction that tells the agent how to do the job. Six are built in: fix a bug, fix a CI failure, handle PR comments, build a feature from an issue, update dependencies (minor and patch only) and raise test coverage. Save your own playbooks on this computer or in the repo as .agentvera/playbooks/*.md files, which reach your team through git.
Safety limits
Because automations run on their own, the limits are set up front.
- Each rule runs at most 1–50 times in a rolling 24 hours, 5 by default.
- At most 2 automatic fixes per branch per day, and only one at a time.
- GitHub is checked every 2 minutes; CI runs and PRs from forks are skipped.
- Comment and issue text is passed to the agent marked as untrusted outside text that only describes the work.
- Before a push, commits are checked for .env, key, .npmrc and credential files; if one is found, nothing is pushed.
Set up your first rule
- 1
Open the project’s Details → Otomasyon → Otomasyonlar tab.
- 2
Pick a ready-made rule or create a new one.
- 3
Choose the event, playbook, agent and landing.
- 4
Set the daily run limit and save; follow the results under Çalıştırmalar.
Questions
Which agents run the jobs?
Claude Code or Codex; Claude Code by default.
What do PR comments and issues need?
The repo’s origin must be on GitHub and you need to be signed in to GitHub on this computer. The CI event works with every provider in the CI/CD tab.
Will an agent push to my default branch?
No. Even with push to the same branch selected, the default branch gets a PR instead, and Automatic mode never pushes to it directly.
Can a PR comment trick the agent?
Only comments from owners, members and collaborators are handled, and the text reaches the agent marked as untrusted. Commits are also checked for secret files before a push.
Related features
Bring your agents to one desk.
Start on the free plan. Download it, add a project folder and open your first agent.