GitHub
Your project board
- #131Rate limits
- #134Audit log
Less coordination.
More progress.
File the issue. Get the pull request.
Your coding agent. Your projects. Your rules.
The same checks and review. Human help for critical cases.
Your project board
Ready to coordinate
Mac mini · coding agent
Capacity available
Start with an issue on your GitHub board.
MergedUpdate the key in your infrastructure, then let Autop retry the checks.
Several projects. Multiple repositories.
A shared pool of runners keeps
work moving in parallel.
The coding agent you already use.
Compute you already have access to.
Mac mini, workstation, or a server you can access. Autop-hosted runners are planned.
Choose how often Autop asks.
Set the level for each project.
Autonomous selected. The same checks and review. Human help for critical cases.
See this level in the workflow ↑Demo only. Your project settings stay unchanged.
For developers building across projects and repositories.
A GitHub organisation you own, Claude Code or Codex installed and logged in, and access to a Mac or Linux machine that stays on—a Mac mini, workstation, or server.
Bounded retries, then a human handoff with a reason. Work is never retried forever.
With your coding agent, on the machine running it. The runner never reads, copies or proxies them.
Merging follows your project’s autonomy level and branch rules. Deployment stays with your own pipeline.
A Development Autopilot is a service that takes issues from your GitHub board to merged pull requests. Autop does it with the coding agent you already use, on your own machine, with your checks and an automated review, under rules you set. Read the full definition →
Claude Code and Codex. Autop runs the one you already have installed and logged in; it never sees your provider login.
No. Every model call and every build runs on your machine. The Autop plane only schedules work, enforces your rules, posts review verdicts and merges by your branch rules; it never clones your repositories.
Yes. One project covers several repositories of one GitHub organisation on one Projects board, and a shared pool of runners keeps work moving in parallel.
From your GitHub Projects board. Issues labelled autop with a priority label, in the Todo column, are picked in priority order; epics, sub-issues and blocked-by links set the sequence.
As much as you choose, per project. Hands-on: you review every pull request. Guarded: checks and automated review, you step in on escalation. Autonomous: work keeps moving and only critical cases escalate.
Yes. A Mac or Linux machine you can access: a Mac mini, a workstation, or a server. Autop-hosted machines are planned.
As a private alpha. Join the waitlist by signing in with GitHub; Autop builds Autop in its own environment.
Autop runs on your machine with your subscription and works across many repositories on one board; hosted coding agents typically run in their cloud, per task, usually one repository at a time.