Autonomous delivery for active repos

Turn issues into PRs from your own control plane.

Autopilot is the self-hostable delivery layer around coding agents: queue work, dispatch isolated sessions, inspect progress, and keep branch state tied back to the issue lifecycle.

What ships with it.

Built for the work around agents: queueing, session isolation, PR handoff, cost limits, and cross-repo visibility.

Queue-first automation

File work once. Autopilot dispatches an agent, opens the PR, and tracks it across every enrolled repo.

Self-hosted control

Run the daemon against your own Supabase project, local clones, and local agent credentials.

Observable sessions

Board, issue, session, cost, effort, and graph views keep the delivery loop inspectable.

Conflict-aware rebase

Generated files, lockfiles, and messy branches take the fastest available path back to green.

Flexible model routing

Choose the agent command and model profile that fit your repository and keep those settings local.

PR handoff

Session handoff markers, branch metadata, and close reasons stay connected to the issue lifecycle.

From setup to first run.

The public repo stays focused on local operation and self-hosted infrastructure.

01

Prepare the database

Apply the bundled Supabase migrations and configure the dashboard environment.

02

Install the CLI

Install the Homebrew binary or build from source on macOS or Linux.

03

Enroll a repo

`autopilot init` in your repo, then start the daemon.

04

Let it run

The daemon picks up ready work, dispatches sessions, opens PRs, and records the result.