Autopilot
Autopilot builds your software project while you are away. You write what you want in plain words and start it once. You get working software, tested, with a record of every step. It is for one developer, or for a person with an idea and a developer friend.
Give it a plan tonight. Wake up to a working app, and proof that it works. Claude Code (the coding agent) writes the code; Python code decides when a task is complete.
Claude Code alone and with Autopilot
| Claude Code alone | With Autopilot | |
|---|---|---|
| Direction | Claude can choose the design as it works. | Your plan sets the design. The gate refuses plan changes. |
| Checks | The model can say that work is done. | Autopilot runs your build, lint and test commands. A task merges only if they pass. |
| Failures | You find and repair a problem. | A stronger model tries again. Autopilot repairs a missing tool or a red main branch. |
| Questions | The chat waits for you. | That task waits. Other tasks continue. |
| Status | You scroll the chat. | ap watch shows tasks, output, progress and usage. |
The full comparison has ten rows. Use Claude Code alone for a small change, a question, or an open design.
How it works
flowchart LR
accTitle: How Autopilot builds a plan
accDescr: Each task runs in a new Claude Code session. Python runs the checks. A pass merges to main, a fail retries on a stronger model, and a blocked task becomes a question while the other tasks continue. At the end, a completion audit adds tasks for gaps.
plan["Plan"] --> task["Next task"]
task --> session["New Claude Code<br/>session"]
session --> gate{"Python runs<br/>the checks"}
gate -->|pass| merge["Merge to main"]
gate -->|fail| retry["Retry on a<br/>stronger model"]
retry --> session
retry -->|blocked| park["Question in NEEDS-YOU.md,<br/>build the other tasks"]
park --> task
merge --> task
merge -->|plan done| audit{"Completion<br/>audit"}
audit -->|gaps| task
audit -->|complete| app["Working app"]
Follow the build
ap watch shows the build in the terminal; the status page shows the same data in your browser (sample data).
Real results
Two real projects built from a plan:
- SecretScan finds leaked secrets in a repository.
- envguard checks
.envfiles against a schema and finds secrets in the git history.
| Measure | SecretScan | envguard |
|---|---|---|
| Tasks merged | 27 of 27: 13 from the plan, 14 from the audits | 21 of 21: 11 from the plan, 10 from the audits |
| Blocked tasks | 0 | 0 |
| Passed on the first attempt | 25 of 27 | 17 of 21 |
| Decisions that needed a person | 0 | 0 |
| Agent time | 2.2 hours, 38 sessions | 1.4 hours, 42 sessions |
| Cost at API prices | $17.13 | $19.01 |
Both runs used a subscription. The envguard audits found 8 real bugs; Autopilot fixed all. envguard is private; numbers come from the run log. A lean rerun of envguard used 39.5 percent fewer tokens per task.
Install
One line. It installs what is missing for your user, with no administrator prompt. Windows (PowerShell):
irm https://raw.githubusercontent.com/manishjnv/AutoPilot/main/install.ps1 | iex
macOS, Linux or WSL:
curl -fsSL https://raw.githubusercontent.com/manishjnv/AutoPilot/main/install.sh | bash
On Windows pick Windows or WSL, not both; WSL only for the sandbox. With uv already
installed, uv tool install dev-autopilot is the same.
Open a project folder and type ap. The first run logs you in to Claude (a paid plan, Pro or Max), then starts.
See What ap does. After a release, run ap upgrade. For a repair or a
second machine, run ap install. Checksums and each step: Install with one script.
Example output
Shortened real output:
task P02-T01 attempt 1 failed: PROBLEM: skip/focus marker added in tests/test_walker.py
session #10 task P02-T01 model=sonnet attempt=2
task P02-T01 done (sonnet, $0.39)
audit: completion audit: 92% complete, 8 corrective tasks (FIX001)
Documentation
| To | Read |
|---|---|
| Build your first project | Tutorial |
| Do one job: a server, phone alerts, an existing project | How-to guides |
| Look up a command, setting, file or term | Reference |
| How Autopilot works and why | Architecture |
Good to know
- Version 0.3.0, an early release. MIT license.
- One CLI agent per session. See limits and runners.
Metadata
Release files for dev-autopilot 0.4.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| dev_autopilot-0.4.0.tar.gz | 347.9 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| dev_autopilot-0.4.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 594.4 kB
Release files / dev_autopilot-0.4.0.tar.gz
| Download URL | dev_autopilot-0.4.0.tar.gz |
|---|---|
| Size | 347.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f3eb0971aae580c615fe809fccf697f7e0fc6210e8286afa509892cd869ecc13
|
|
BLAKE2b-256 checksum How to use checksums |
e35762763d39e229205c3e8f494e37cd9baebae2367ff4ec8d9a99d0233e6ba7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 12, 2026.
Transparency logRelease files / dev_autopilot-0.4.0-py3-none-any.whl
| Download URL | dev_autopilot-0.4.0-py3-none-any.whl |
|---|---|
| Size | 246.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
d7691dbb6d30c392ca9921461b9bf70a440fb4a5837dc5beea5c39d395b3f552
|
|
BLAKE2b-256 checksum How to use checksums |
5738de7d4aa0fdfc92255a5f2e4a8f54263ee1e96ab1abacdb41c0d61d50de17
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 12, 2026.
Transparency log