Don’t let one agent grade its own homework.
The agent that wrote the code has the same blind spots when it reviews the code. A review flow hands your spec or diff to a separate reviewer — and loops until the findings are gone.
It reviews its own work and calls it clean.
You ask the agent that just wrote the handler to check its own work. One agent can’t catch the blind spot it just wrote in.
Review your change before I open the PR.
Clean handler — it follows the existing route style and reads well. No issues. Good to merge.
Without a second agent, the merge looks reviewed and isn’t.
The reviewer catches it. Your agent fixes it.
Your agent hands the diff to a hosted reviewer — a vendor you choose — and waits for the verdict. Round two comes back clean.
Get an independent review before I open the PR.
The reviewer flagged the missing authorization check. I added an org-admin guard and re-submitted. Second round came back clean.
With a review flow, work gets checked, fixed, and re-checked before it’s done.
The kcap mcp flows server hands your spec or diff to a hosted reviewer you choose, independent of the agent driving the flow. It returns findings, your agent addresses them, and it re-reviews until it signs off — the whole loop event-sourced on your server. See Hosted agents and PR review.
Ship work that’s already been reviewed.
Start free, run a daemon on your repo, and let a separate agent check your agent’s work before you merge.
Fix flaky auth-token refresh test
Tried mocking the clock first — abandoned after the race persisted. Root cause: token cache TTL rounding. Patched in auth/cache.ts, added regression test. Two approaches rejected, one shipped.