What problem does it solve?
Autopilot coordinates unattended harness-infra improvement cycles by selecting the oldest open autopilot issue or generating a first-principles research ticket, then driving end-to-end through the ship-spec pipeline to land a ready-for-review PR. It operates entirely on harness-infra tasks and runs in its own per-run tmux session, enforcing caps to prevent overload and providing clear session lifecycle management.
Core Features & Use Cases
- Queue-driven issue selection: picks the oldest actionable autopilot-labeled issue with no linked PR.
- First-principles research branch: if queue is empty, runs harness-audit to file a research ticket and builds a plan via /ship-spec.
- End-to-end build pipeline: /ship-spec owns implement/eval/pr-audit and creates a ready-for-review PR, with a selection rationale and session lifecycle management.
- Safe concurrency and governance: caps limit number of open/autopilot PRs per UTC day and total open; dry-run mode to preview decisions.
- Session and artifacts management: tmux sessions named after the work branch, memory logs, and restore-safeguards.
Quick Start
Configure the autopilot cron to monitor an autopilot-labeled queue and let it autonomously file issues, build plans with /ship-spec, and create ready-for-review PRs.