It takes the project manager's job.
Not a task generator. Autopilot interviews you for a brief, plans the work, assigns it to people who have the capacity, chases the updates, re-plans around the slips and escalates what is stuck — to the level of autonomy you set, over the stretch of project you point it at.
Included with the Business plan. Configured per project — there is no organisation-wide switch, by design.
Six combinations, chosen per project. Work due past the horizon is not planned, not graded, not re-dated, not reassigned and not chased — and the run summary says how many items it left alone.
Two questions, and they are not the same question.
Most “AI PM” settings are one slider. Autopilot has two, because how much it may do without asking and how much of the project it is answerable for are genuinely independent — a team can want the next fortnight run autonomously and nothing at all beyond it.
Autonomy — how much it may do without you
- Draft & Propose — the default. It builds the board, picks owners and stops. Nothing applies and nobody is contacted until you approve it.
- Draft, and apply safe changes — check-ins, risk logs and tasks from explicit meeting action items land on their own. Reassignments and date moves still wait.
- Fully Autonomous — it acts, and every change is still listed and individually reversible.
- Two proposals never apply themselves at any level: naming a team lead, and creating a team.
Horizon — how far ahead it is running
- Up to a milestone — it plans and manages the work leading to one milestone, then stops.
- Start to finish — out to the delivery date. It asks for a line on every milestone first, because it can only plan from what you tell it.
- Anything due past the horizon is left completely alone, and the run summary counts it.
- Every project configured before the horizon existed was migrated to the SMALLER scope, never the larger one.
Nine things a project manager does. It does all nine.
This is not a wish list. Every item below is exercised end to end, on a real project, in both the proposal mode and the autonomous one, before a release ships.
Breaking the work down
A brief becomes phases, epics, tasks and checklists — compressed to fit inside the horizon you set, rather than sprawling out to whatever the model felt like.
Deciding who does what
It assigns from your real members and weighs their load across every active project, not just the one in front of it. On a private project it can only reach people who can actually open the board.
Chasing the status update
It asks the owner how a task is going and reads the answer as written. “About three days behind” re-dates the task — once, not on every cycle until you stop replying.
Re-planning around the slip
When something genuinely moves, it works out what depended on it, moves those too, and tells the people who own them what changed.
Escalating what is stuck
Blocked work goes to a named human — the leads of the team the work belongs to, and the project's own leader as the fallback. Not to a log nobody reads.
Noticing a team with no lead
It proposes a lead, and proposes creating a team where the work needs one. Both always wait for a person — at every autonomy level, without exception, because a team is an organisation-wide object.
Closing what is finished
Connect GitHub and a merged pull request closes its task, so the board stops being a second place to report the same thing.
Writing the run-up
Every cycle ends in a summary of what it did — including how many items it deliberately left alone, which is the number a status report usually omits.
Knowing when to stop
Run the same cycle twice on an unchanged project and the second proposes strictly less than the first. A manager who repeats yesterday's suggestions is noise.
One run, eight moves.
Autopilot runs on a cadence you choose — manually, daily or weekly. Each run walks the same eight steps, and ends by handing you back a list you can undo.
- 01
Interview
Five questions, one at a time.
- 02
Plan
Phases, epics, tasks, checklists.
- 03
Assign
Real people, real capacity.
- 04
Check in
And read the answer.
- 05
Ripple
Move what depended on it.
- 06
Escalate
To a named human.
- 07
Summarise
Including what it left alone.
- 08
Reversible
Every change, individually.
It interviews you. You don't write an essay.
A blank “describe your project” textarea is where this kind of feature usually dies. Autopilot asks five short questions instead, one at a time, and composes the brief from your answers.
The parts a wrong guess would ruin — the delivery date, the budget, the kind of project — are read by a parser rather than invented by a model, because a fabricated date silently compresses a year of work into a fortnight. Where the parser refuses and the model resolves it anyway, you are told in words what it read, beside a field you can correct.
- 1In one sentence — what does this project deliver?
- 2When does it need to be live?
- 3What's the budget, or the constraint that really binds?
- 4How will you know it worked?
- 5Anything Autopilot should stay away from?
Two of the five are optional and say so. The date is read by a parser, not by the model — and where it cannot read one, it tells you in words what it thinks you meant, next to a field you can edit.
Autonomy is only worth having if the edges are real.
Each of these is configured on the project and enforced when the run happens — not a label on a settings screen.
- VIPs, with a ceiling on the hours any of them can be handed. Set it to zero and they are never auto-assigned anything.
- Stakeholders who get the summary whether or not they own a single task.
- Communication hours, evaluated in each recipient's own timezone rather than yours.
- Connectivity granted per project — GitHub, chat, calendar — where an ungranted switch genuinely changes behaviour instead of dimming a label.
What we don't claim
- It does not read anyone's calendar free/busy — it reads declared work hours.
- It does not reshuffle a plan because a meeting moved.
- It does not schedule meetings with people outside your workspace, and it does not send email on your behalf.
- There is no Figma integration, and no switch pretending there is one.
- A team lead and a new team are always proposed to a person, at every autonomy level.
- Assigning someone a task does not grant them access to a project they could not already open.
The five worth answering before you turn it on.
Does it ever act without asking?
What does it use to judge who is free?
What happens to work due after the horizon?
What if there is nothing to plan from?
Which plan is it on?
Start it on Draft & Propose. Move the dial when it earns it.
Every change it makes is listed, attributed and individually reversible — which is what makes trying the next level up a decision rather than a leap.
Business plan · configured per project · no credit card to start