Plannotator’s async Inbox routes human feedback to coding agents
Plannotator is a local browser-based review workspace for coding agents. Its Inbox stores human feedback as persistent messages and routes later replies to specific agent session connections. A Juejin project analysis examines message persistence, session routing, deduplication, delivery confirmation and crash recovery. It also warns that having an MCP interface does not mean every host can automatically receive follow-up messages. The analysis records Plannotator at No. 2 on GitHub Trending on November 17, 2026, but says this time-specific popularity snapshot does not establish delivery reliability or production readiness.
The async Inbox offers an alternative to keeping human review inside a long-running synchronous tool call. Persistent messages, explicit delivery states and recovery handling can help preserve the link between feedback and the intended agent session, particularly when several agents are reviewed in parallel. Actual delivery still depends on the connected host supporting session wake-up or steering.
日期:2026-11-17 GitHub Trending 排名:第 2 位;榜单采集时间:16:00:53(北京时间)
Agent 写了一份重试方案,你在第三段标出“这里不能自动重放支付请求”。下一步最容易出问题的,往往不是批注界面,而是这句话怎样回到正确的会话:原来的工具调用还在等吗?会话重启后,答复还在不在?两个终端同时恢复同一个 Agent,会不会把同一句“继续执行”送进去两次?
Plannotator 从浏览器里的计划批注工具长出了一个 Inbox。它把人的意见存成消息,再交给具体的 Agent 会话连接投递。值得细读的部分就在这个变化里:从“函数等一个返回值”,走向“消息先留下,答复稍后到达”。
📋 项目概览
| 项目 | 内容 |
|---|---|
| 主仓库 | backnotprop/plannotator |
| 定位 | 面向编码 Agent 的本地浏览器审阅界面与异步 Inbox |
| 主要语言 | TypeScript |
| 主要技术 | Bun 服务端、React 界面、宿主插件与 MCP 接口 |
| Stars | 12,804,来自当日采集快照 |
| Forks | 1,272,来自当日采集快照 |
| 许可证 | MIT 或 Apache-2.0,使用者可二选一 |
| 本文上手版本 | v0.28.67 |
| 重点 | 消息持久化、会话路由、投递去重和崩溃后的恢复边界 |