Agent Review Inbox

A shared queue where coding agents wait for your review

Problem

Developers increasingly run several coding agents locally, and when they finish someone has to dig through diffs, logs, and PRs across terminals and branches. A desktop inbox where agents wait for review shows the need to funnel agent output into one triage point. And red-squiggle tooling for teams of agents hints that multi-agent collaboration is already here.

Solution

A local-first review inbox: agents report finished tasks through a light CLI or MCP adapter with change summaries, diffs, screenshots, and test results. A desktop or web panel groups items by repo and branch, lets you batch-approve or reject with comments, and writes feedback back into the agent context. Filters by repo, branch, and agent process.

Users

Solo developers running multiple coding agents, and tech leads managing agent output in small teams.

MVP

Local CLI and MCP reporting endpoints; desktop panel groups pending changes by repo; each item shows diff summary, test status, and agent notes; one-click approve or reject with comments sent back; everything stored locally, no account required.

Revenue

Free personal tier, paid team tier for shared inbox, audit log, and Slack notifications at $5–8 per seat/month.

Why now

Coding agents are moving from single completions to long autonomous tasks, producing more output than humans can review one by one, yet no lightweight local-first triage tool exists. Indie developers can build only the adapter and inbox, not the model layer.