From zero to your first shipped ticket
What happens between writing a ticket and seeing it shipped or escalated.
The setup wizard ends on a blank ticket form. Here's what happens from there.
Write the ticket
Give it a title, a description, and, this is the part that matters most, an acceptance criteria checklist. A ticket can't move to Ready without one, because the reviewer and the independent verifier both check the diff against that list item by item. A vague ticket produces a vague result; a specific, checkable one is what the pipeline is built to satisfy.
Move it to Ready, then Run
Tickets move through Draft → Ready → Queued → Running → Needs review → Shipped (or Failed). From Ready, either click Run now yourself or leave it to Autopilot to pick up by priority once its dependencies have shipped.
Watch it run
The ticket's live view follows the same pipeline described in the introduction:
Implement
The agent writes the change in a fresh session, in its own isolated copy of your repository.
Checks
Your build, lint, typecheck and test commands run as hard gates. A failing check blocks shipping regardless of what the AI reviewer says. See Auto-detected checks for how these are configured.
Review and verify
A reviewer cites file-and-line evidence for every acceptance item. A separate verifier, in a fresh session that never saw how the code was written, checks that evidence against the diff and the ticket on its own.
Security
The change is scanned for security issues. Low-risk findings are fixed and re-checked automatically.
Ship or escalate
Everything passing moves the ticket to Shipped: committed to your working branch, or opened as a draft PR, depending on your branch strategy. Anything short of that lands in Needs review with an escalation report explaining what was tried and why it stopped, instead of a half-finished commit.
Decide what happens next
On a shipped ticket you can Approve & commit it if it opened as a PR awaiting review, or Revert it if it turns out to be wrong. On one that needs review, you can Retry with a hint (pointing the agent at what to fix), Skip it, or edit the ticket and send it back to Ready. Every ticket keeps a downloadable post-mortem of exactly what happened, pass or fail.