Autopilot Guide
You decide what gets built — at two gates: plan approval and merge. Agents do everything between. No CLI commands to memorize.
Fastest start
Then type intent in the Mind tab. That's the whole manual.
Type intent
Describe what you want in plain language — in the Mind tab's intent box, or via the API. barkcli classifies it into a card + spec, offline if needed.
POST /api/intake {"text": "Add Google OAuth", "kind": "feature"}Approve the plan
The agent proposes a decomposition (child cards + acceptance criteria). You approve, edit, or reject — this is the first human gate. Approval writes the exact same cards as plan --tasks.
POST /api/autopilot/approveAgents work
Coding agents pull atomic work packets (packet_claim), implement, test, and complete them. No human commands — Mind shows live phase and counts.
GET /api/autopilot/statusReview & merge
Completed work is validated against acceptance criteria, tests, and commits. You merge (second human gate) or request changes. Checkpoints + undo cover recovery.
POST /api/reviewAgent loop (for coding agents)
Agents steer through MCP — 56 tools including the autopilot set:
autopilot_status— phase, gates, next actionpacket_claim— atomic top-packet claimautopilot_propose— propose a plan (creates gate)task_complete / task_fail— report outcomes