Review gates
A review gate pauses a run at a step and waits for you. Use gates on the decisions you care about most, so the run does not spend money acting on a script or an edit you would have rejected.
Adding a gate
Tick Review gate on any step in the editor, or set review: true in YAML:
- id: ai_cut
processor: ai_agent
review: true
When the run reaches that step, it stops and shows you what the step produced.
Answering a gate
The run view shows the gate inline. What you see depends on the step:
- A script or an edit. Read it, then Approve, or switch to Edit to change it and Approve with edits. Reject stops the run.
- A set of concepts. Pick one with Choose this concept, or Write my own direction and describe what you want instead. No preference lets the AI choose, ↻ Suggest again asks for a fresh set of ideas, and Cancel run stops.
- A segment plan, showing which kind of content goes where. Same approve, edit, or reject choices.
Approving with edits is usually better than rejecting: the run continues from your version instead of starting the step over.
Reviewing b-roll clip by clip
To vet b-roll before it is placed, put a review gate on the b-roll step. At the gate you see the planned clips and can approve them, edit the selection, reject, or ask for new ones, the same choices as any other gate.
Taking your time
There is no deadline on a gate. A run can sit waiting for hours or over a weekend, and when you answer it resumes exactly where it left off. Nothing before the gate is repeated.
What happens if you reject
Rejecting ends the run at that step. The step produces nothing and nothing after it runs, so nothing downstream gets generated or charged for. When you are ready to try again, use the ↩ control on that step in the run view: the work before the gate is reused rather than redone.