Kapacitor/PR review
Your agent already reads the code. Now it can read what your teammate tried before they wrote it.
Without the session
You ask your agent why Sam changed it. It only has the code.
5?Every other job in this repo uses 500.
At 5, throughput drops by two orders of magnitude.
Looks like a debug value left in by mistake. Restore it to 500.
Without the session, the agent confidently guesses wrong.
With the session
Your agent pulls the session behind the PR and reads the load tests that led to the change.
5?Sam load-tested 500, but the database locked up at p99.
They tried 200 next, but the writer ran out of memory.
At 5, the job stayed stable for 30 minutes. The PR is trading throughput for stability until the writer is sharded.
With the session, the agent stops guessing.
How it works
The kapacitor review MCP server hands the PR’s linked sessions to your agent at review time: file context, prior test runs, and the FTS-indexed transcript. Read the mechanics in PR review.
Kapacitor is in private preview. Bring us one repo and we'll wire up kapacitor review for your next pull request.
Rather start a conversation? Talk to the team — we’re building with teams that already use coding agents.
Built by the team behind KurrentDB — event streams in production are what we do. Coding agents just produce a new kind.