Review and approve a run

A run waits when the pipeline reaches a gate. The run status is waiting_for_human. Approve continues the run; reject sends your note back as feedback. Delivery, when it happens, is a local commit. Kusaw never merges or pushes.

Default pipelines have no gate. You only wait when kusaw.yaml includes one, for example a human-check gate before deliver.

kusaw serve has to be running to pick up approve and reject.

Where the run waitsCopy Anchor Link

The run is waiting_for_human. On the Dashboard that maps to Blocked. The run page heading is Waiting for you plus the gate name and its prompt. Waiting time does not count toward the run's time limit.

If the run is not waiting, approve and reject are refused: Run "<run>" is not waiting for a human.

What to look at, in orderCopy Anchor Link

On the run page, or in kusaw status <run>:

1. SUMMARY — the delivery note once deliver has run; empty before that.
2. Diff — the repo tabs: branch, worktree, and the commit that was delivered. Open the worktree if you want the full diff.
3. Verification output — the commands under ## Verification and whether they passed, on the repo tab.
4. Findings — review findings from the last try.
5. Evidence — when the run has delivered, SUMMARY includes the verification evidence from that deliver. There is nothing extra to look at before then.

Approve or rejectCopy Anchor Link

Approve does not need a note. Reject does (reject needs a note.). Keep a note under 4000 characters.

Approve. The run goes to the front of the queue and continues at the step after the gate. When that path includes deliver, each passed repo gets one squashed commit on the shared branch factory/<task>-<seq>. That commit stays local. Kusaw never merges and never pushes.

Reject. Your note is feedback.

• If the gate is inside a loop that still has tries left, the run goes to the front of the queue and the next try sees the note.
• If the gate is at the top level, or the loop is on its last try, the run ends needs_attention (reason gate_rejected). The note is prefilled for Requeue. See Rerun, requeue, resume or steer.

Dashboard copy next to the buttons:

• If you reject, this note is sent to the next try as feedback. (gate in a loop)
• If you reject, this note is kept for Requeue. (gate at the top level)

If it goes wrongCopy Anchor Link

• Run "<run>" is not waiting for a human — the run is not at a gate. Check kusaw status <run> or the Runs tabs.
• reject needs a note. / Add a note to reject. Approve doesn't need one. — reject with --note, or type the note on the run page before Reject.
• Approve or reject stays pending — kusaw serve is not running. The request waits until serve is back.
• You meant to stop, not reject — stop or dismiss instead of reject.