Gates & reviews

Human-in-the-loop by default: approvals, rework loops, and who's allowed to approve.

Between phases, a run stops at a gate and waits for a human. That's the core safety property: the agent never advances past a phase you haven't seen.

Approve or request changes

At a gate you see the phase's full output — the transcript, diffs, check results, published artifacts. Approve moves the run forward. Request changes sends your note back as feedback and the agent reworks the same branch, then returns to the gate. You can also submit a rework at any time from the editor's native code review — leave comments on the diff and send them as one "request changes".

Who may approve

A phase can restrict approvers:

phases:
  - id: coding
    gate: true
    approvers:
      - github:alice
      - linear:9f8e-…-team-lead

Approval reuses the reviewer's external identity — the GitHub or Linear account they signed in with — so the policy names people you already know. With no approvers: list, any member of the organization may approve.

Notifications

Notifier connectors (Slack, Discord, Microsoft Teams, Telegram, or a plain webhook) announce gate arrivals and results where your team already looks, with published artifacts attached.