Close the agent review loop
Track what an agent changed, verify it as a human, and reopen only when another correction is needed.
6 minIn this guide
Agent return
An agent can report each pin as changed, blocked, not applicable, or not located, with a summary, reason, changed files, commit, and pull request. Repeated delivery with the same idempotency key is safe; conflicting content under that key is rejected.
Human verification
A changed result moves an open or reopened pin to correction ready. Only a human can accept a correction or reopen an accepted pin. Agents cannot accept their own work, and invalid state transitions are rejected.
- Normal flow: open → correction ready → accepted.
- If verification fails: accepted → reopened → correction ready.
Record an execution and accept it as a human
An agent reports work against the capture’s captureId and each pinId. Repeat a delivery with the same key only when the result is unchanged; a different summary, files, or status needs a new key. Unknown pins or captures are rejected without echoing private comments.
A person accepts a correction or reopens an accepted pin from the review UI. Agents cannot accept their own work. After a human reopen, the intended retry is a second changed result. Leave anonymous loop metrics off unless you opt in.
- Publish a changed result for the same
captureIdandpinId, then confirm the viewer shows the pin as ready to accept. - Reuse a delivery key only when the result is identical; mint a new key when the files, summary, or status actually changed.
- If verification fails, reopen as a human, publish a second result, accept again, and keep the before and after capture ids.