Plan review
Approve, comment on, and steer a plan before any code is written.
Before an agent writes code it writes a plan — in prose, describing what it intends to change and why. On projects where plan approval is on, nothing is built until you approve it.
This is the cheapest place to correct course. Redirecting a plan costs one comment; redirecting a finished PR costs a review cycle and the work that went into it.
Approving
A ticket waiting on you sits in awaiting_approval, and the plan appears both in the
dashboard and as a comment on the ticket in your issue tracker. You have three options:
- Approve — the developer agent starts immediately.
- Request changes — leave a comment saying what's wrong. The planner revises and comes back for approval again.
- Close — the ticket stops here.
Whether approval is required is set per project. See Autonomy levels to turn it on or off.
Commenting on a plan
You can comment on the plan as a whole, or on an individual task within it. Each comment opens a thread, so a specific objection stays attached to the specific task it's about instead of getting lost in a general discussion.
When the planner revises, it responds to every open comment and marks each one addressed, partially addressed, or not addressed, with its reasoning. That last verdict is the useful one: an agent that says "I didn't do this, and here's why" is far more informative than one that silently ignores you or claims success.
Unresolved comments stay visible on the next round, so nothing quietly drops.
When an agent asks you a question
Agents don't only wait at the approval gate. If one hits a genuinely ambiguous decision —
a requirement that could reasonably mean two things, two approaches with materially different
consequences — it stops and asks rather than guessing. The ticket moves to awaiting_input
and the question is posted on the ticket.
Answer in your issue tracker or in the dashboard and the run resumes from where it paused. Nothing times out, and nothing is lost while it waits.
This behaviour is on at Supervised and Balanced, and off at Autopilot — a team that has opted out of gates has also opted out of being interrupted.
Your answer is treated as information, not as instructions to follow. An agent won't take directives from the text of a comment, which keeps a ticket comment from becoming a way to redirect an agent that shouldn't be redirected.
Keeping the ticket in sync
If review changes the scope of the plan, the agent updates the ticket to match, so the tracker doesn't drift from what's actually being built.
Billing
None of this costs anything on its own. A ticket is billed once it reaches a pull request, so plans you reject, revise, or close never appear on your invoice — see Plans, usage & limits.