Documentation
Autopilot is a workflow-driven AI operator for real engineering work.
Autopilot keeps authored policy in git, operational state in the orchestrator, and secrets/runtime state on the worker.
Where to start
- What is Autopilot — the mental model
- Architecture — orchestrator, worker, truth boundaries
- Quickstart — get running locally
- Operator Guide — CLI workflows, inbox, approvals
- Providers and Handlers — providers, handlers, and surfaces
- Packs and Distribution — install integrations via the pack system
- Conversation-Assisted Operation — chat bindings for task actions
- Telegram Surface — the first real surface pack example
- Cloud and Deployment — truth layers, multi-worker, deployment patterns
- FAQ — common questions
Core idea
Tasks are intent. Workflows decide what happens. Workers execute where access exists.
The system is designed around a small set of stable primitives — tasks, workflows, runs, workers — with multiple clients (CLI, notifications, chat surfaces) operating over those primitives. There is no single app that owns the product. The orchestrator owns operational truth. Workers own runtime execution. Git owns authored policy.
Integrations arrive as packs — installable units that deliver providers, handlers, workflows, and more into your .autopilot/ directory via autopilot sync. Surfaces like Telegram, Slack, and Discord are built over the same provider/handler primitives, not hardcoded.