Your backlog, turned
into pull requests.
AutoPilot takes the next ticket off your board, writes the change in your repository, and opens one pull request for your team to review. It never merges. Nothing reaches your main branch without a person saying yes.
From card to shipped PR
// 5 steps, then youRead
It takes the top card in your To Do column — and skips anything it judges unclear.
Plan
It reads your repository and decides which files the change touches.
Build
It writes the change and pushes it to its own branch. Never to yours.
PR
One pull request per card, with the reasoning attached.
Advance
The card moves to Code Review with a comment recording what it did.
Step six is yours. The pull request sits and waits for a human. AutoPilot has no permission to merge it, and no way to give itself one.
What it does, and what it will never do
The second list is the reason teams let it near a real repository.
It does
- Work one ticket at a time, start to finish
- Read your repo before it proposes anything
- Open one pull request per ticket — small enough to actually review
- Refuse a card it judges unclear, and say why on the card
- Write back what it did, so the board stays the record
- Run on a schedule you set, or not at all
It never
- Merges anything, or pushes to your default branch
- Touches CI configuration, environment files, or secrets
- Commits anything that looks like a credential
- Exceeds its per-run limit on files changed
- Deploys, or touches production
- Approves its own work
SOSA™ — Supervised Orchestrated Secured Agents — is the operating standard behind that second list: every agent runs inside a defined scope, with a named human on the other side of anything that changes something real.
See a full run, end to end
The deeper walkthrough follows one card all the way through: the files it chose, the pull request it opened, and the point where it stopped and waited for a person.
See the walkthroughWhat it needs from you
Three things. Setup is a call, not a project.