- 🔧 Configure an org chart of agents using simple YAML files in a
.auto/directory alongside your codebase - 🎼 Compose agents and triggers into automations that can be triggered by events from your workspaces (Slack/Github) or your production systems (Datadog/PagerDuty/etc.)
- 🚀 Deploy them serverlessly on git merge into sandboxes with lift-and-shift parity to your local development environment
- 🏎️ Steer and monitor them across Slack, GitHub, and the Auto dashboard
What teams build with it
You can use auto to build simple (but effective) automations:- Issue triage — label- and mention-driven agents that classify, reproduce, and route incoming issues.
- Incident response — webhook-woken responders that investigate alerts, coordinate in a war-room thread, and draft fixes.
- Code review — a reviewer on every PR with ranked findings, a managed check, and re-reviews folded into the same session on push.
- Agent fleets — a chief-of-staff in Slack with memory dispatches dozens of parallel workstreams, shepherds every PR to green, unblocks stalled work, and loops you in only when your call is required.
- Autoresearch and self-improvement — multi-agent loops that test hypotheses on a fleet, or propose improvements to the app and
.auto/itself. - Lead engine — leads arrive by webhook; the agent researches, scores, drafts outreach, and posts to Slack for human approval.
Start here
Quickstart
Go from zero to a fully deployed agentic workforce in under 15 minutes
Concepts
Understand the nuts and bolts of the Auto programming and runtime model.
Examples
Complete, working
.auto/ directories you can copy