Review PRs with the reasoning, not just the diff.
Your agent already reads the code. Now it can read what your teammate tried before they wrote it.
Another PR you don’t have time to understand.
− batchSize: 500+ batchSize: 5You ask your agent why Sam changed batchSize to 5. It only has the code.
Why did Sam drop the batch size to 5?
Every other job in this repo uses 500. At 5, throughput drops by two orders of magnitude. Looks like a debug value. Restore it.
Without the session, the agent confidently guesses wrong.
The reason was in Sam’s session all along.
Your agent pulls the session behind the PR and reads the load tests that led to the change.
Why did Sam drop the batch size to 5?
Sam load-tested 500 — the database locked up at p99. They tried 200 next, but the writer OOM’d. At 5, the job stayed stable for 30 minutes. Trading throughput for stability until the writer is sharded.
With the session, the agent stops guessing.
kcap review <pr-url> launches your agent with the kcap mcp review tools, which hand it the PR’s linked sessions at review time: file context, prior test runs, and the FTS-indexed transcript. See PR review.
Review your team’s next PR with context attached.
Start free and wire kcap review into your next pull request — bring one repo and the agents your team already runs.
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.