Review requests (alpha)

Ask a teammate to approve changes before they're applied.

Reviews are part of the alpha collaboration track.

Request a review

In the Changes panel, click Request review instead of Apply. A modal asks:

  • Reviewer — pick from team members with at least Commenter role.
  • Optional message — context for the reviewer.

Reviewer gets a notification. Run is paused.

Reviewer experience

Reviewer opens the run from the notification. They see:

  • The original task text.
  • Your @-mentions.
  • The agent's reasoning.
  • The full diff (read-only — they can't edit).
  • Approve / Reject buttons + a comment field.

Decisions

  • Approve — applies the changes (with all guards firing as normal). A receipt is issued tagged with both your user_id and the reviewer's.
  • Reject — discards the staged diff. You get a notification with the reviewer's comment.

Either way, the decision is recorded in the activity feed and the receipt audit chain.

Multiple reviewers

(Roadmap.) Today: one reviewer per request. Coming: require N approvals before apply.

Comments

Either side can leave comments on the run. Comments are notification-bearing — the other party sees them in real time.

The conversation is preserved in the run's history alongside the receipt.

Why this matters

Two reasons:

  1. Trust — a senior dev can vet diffs from junior devs (or from the agent itself in autonomous mode) before they touch the codebase.
  2. Compliance — for environments where AI-generated code requires human approval before commit.