Cadora · human-in-the-loop
Cadora drives a coding agent through a gated workflow and pauses at the steps a human should sign off on. This is the journey a reviewer takes — from a run parked at a gate to a decision that moves it forward.
You start a gated run — cadora run … --hitl --review-file — and open the dashboard. It's the operator's map: every node, its cost, and its state. Nothing asks for you yet; the agent is working.
The first node finishes and the run parks. An amber callout rises to the top of the page: a node is waiting for your decision, and it hands you exactly the documents that node produced — as links, not a wall of raw JSON.
The gate is fail-closed and patient. Started with --review-timeout 0, it waits indefinitely — walk away, come back tomorrow, the work is preserved.
Click a document to open the rendered file, or preview it inline without leaving the panel. The reviewer sees exactly the diff this stage produced — scoped, not the whole tree.
Four specialist agents (document, policy, medical, financial) + a supervisor synthesizing APPROVED / MANUAL_REVIEW / DENIED.
Before deciding, talk to the work. Pick a document, then ask a question or describe a revision. The parked run drives the same agent that wrote the draft — scoped to that document — and answers in place: a question is answered, a revision rewrites the draft so you can see it before you accept it.
Each ask or revision is a real turn on the agent — you're questioning the model that wrote the draft, not a summary of it. A revision rewrites the document in place, so approving keeps the version you just read.
Three ways forward, each honest about what happens next. Approve releases the next node. Request changes re-runs this stage with your comments woven into its prompt. Abort stops the run. Your comment travels with the decision.
While you're deciding, the page stops auto-refreshing — it will never wipe a half-typed comment or move a button out from under your click.
Your decision reaches the live run. requirements turns green — clean, approved — and the panel advances to the next gate: design. The comment you left is already in the design node's prompt.
Every gate cleared, the run finishes and its evidence pack is sealed. The DAG reads at a glance — three green nodes, each stamped with its gate and review outcome. The audit trail records who decided what, and when.
The screens above reproduce the live Cadora dashboard exactly — rendered as editable HTML rather than raster captures, so they can be lifted into Figma or iterated directly. Every gate is fail-closed, patient, and recorded: the human stays in the loop, and the evidence pack remembers who decided what.