R050 · AI's effect on people › Human verification of AI output

Plannotator Inbox: agents ask, humans answer later, nobody blocks

Read the original

human-oversightasync-reviewagent-harnessagent-protocols

Source: André Lindenberg's LinkedIn post (2026-11-11) on the new Inbox feature of Plannotator, an open-source (MIT / Apache-2.0, about 10k stars) local review tool for AI coding agents.

TL;DR

Most coding agents ask for human input by blocking: the session sits open, holding its context, until someone answers. Plannotator Inbox flips that. Agents post questions, plan reviews, files and guided reviews to one local window and keep working or end their turn. The human clears the queue in one pass, and each answer is delivered back to its session as the agent's next turn. The human becomes an asynchronous reviewer across many agents, not a synchronous gate on each one.

What Plannotator is

A browser-based review surface that sits between a developer and their agents. It wires into each agent through that agent's own extension points (hooks, plugins, skills, slash commands); one installer detects installed agents and configures them. Supported: Claude Code, Codex, Copilot CLI, Gemini CLI, OpenCode, Kiro, Droid, Amp, Pi, T3 Code and others; anything else can connect over MCP. Built with Bun and TypeScript; state lives locally under the user's home directory, with no telemetry beyond a release check.

Four surfaces:

  1. Plan review. When an agent leaves plan mode, a permission hook fires. A local server reads the plan from the hook payload and opens a review page. The reviewer annotates and approves or denies; a denial returns structured feedback, and the revised plan is shown as a diff against the previous one.

  2. Code review. Reviews uncommitted diffs and GitHub PRs or GitLab MRs (also GitButler, jj, Perforce). Line comments go back to the agent; AI reviewers can also comment on the diff.

  3. Annotate. Mark up markdown, folders, fetched URLs, rendered HTML, or the agent's last message, and send the annotations back.

  4. Inbox (new). One window where many agents leave messages and requests while they keep working. A reply comes back as the agent's next turn. On recent Claude Code versions the agent ends its turn instead of waiting, and the decision arrives later as a message.

Architecture

Why it matters

Tradeoffs

Failure modes

Review checklist

Connections

See R050 on the knowledge map

Part of the Research notes on nowucca.com. Figures and claims are the source's own unless the summary says otherwise.