Automations

Scheduled work, security checks, and factory loops.

An automation opens sessions for you. It is a prompt, a repository, and a trigger.

Use automations for work that should happen without a person remembering to start it.

Built-ins and templates

Other useful templates include bug-fix automations, code-quality sweeps, agent-readiness audits, pull request or merge request review, wiki refreshes, CI repair, dependency remediation, incident triage, product analytics digests, Slack digests, and environment-health checks.

The core primitives

PrimitiveWhat it controls
PromptThe work the automation should do.
RepoThe connected repository it runs against.
TriggerSchedule, GitHub/GitLab event, webhook, Slack, or Linear signal.
Enabled stateWhether Ara should keep opening sessions.

Automations use the same building blocks as manual sessions. They can use the repo environment, scoped secrets, native Codex memory, and MCP tools.

Start with low-risk work. Good first automations find issues, open draft PRs or MRs, or report findings. Let guardrails decide how far they can go.