Plannotator is an open-source platform designed to review and validate plans and code generated by AI coding agents.
The platform provides a centralized interface where developers can:
Review AI-generated plans
Annotate proposed actions
Approve or reject tasks
Inspect code changes
Provide structured feedback
Improve agent outputs
Maintain human oversight
Rather than replacing developers, Plannotator aims to keep humans involved in critical decision-making during AI-assisted development.
As AI coding agents become increasingly capable, developers face a growing challenge: ensuring that AI-generated plans and code changes align with project requirements before they are executed. Plannotator addresses this problem by acting as a review layer between developers and AI coding agents.
Instead of generating code itself, Plannotator focuses on making AI-driven development more transparent and controllable. It allows teams to review, annotate, approve, reject, and refine agent-generated plans and code changes before they affect a project.
Download Plannotator v0.28.57 - Software Mirrors |
|---|
Plannotator v0.28.57 for Windowsplannotator-win32-x64.exe | 205.35 MB plannotator-win32-arm64.exe | 190.99 MB |
Plannotator v0.28.57 for macOSplannotator-paste-darwin-x64 | 93.62 MB plannotator-paste-darwin-arm64 | 85.03 MB |
Plannotator v0.28.57 for Linuxplannotator-paste-linux-x64 | 104.07 MB plannotator-paste-linux-arm64 | 104.17 MB |
Plannotator v0.28.57 Source Code |
Plannotator v0.28.57 Release Notes:Follow @plannotator on X for updatesMissed recent releases?
What's New in v0.28.57TL;DR
Plannotator InboxPin artifacts, and the Artifacts pageYou can now pin an artifact (a file or picture in a thread) to come back to it. The pin sits on a card in the thread's Artifacts grid (top left, shown on hover and always once pinned), in the file viewer's bar, and in the pane header. With pins in a thread, its Artifacts grid shows "Pinned" first, then "Everything else". With nothing pinned, the grid looks as before. The sidebar has a new Artifacts row, above Reviews. It opens a page with every thread's artifacts, newest first and grouped by day, with All and Pinned tabs, chips for Images, Pages, Documents and Other files, Smaller and Larger, and "Show archived" in its filter menu. A tile opens its file or guided review in its thread, and Back returns to the page. Pins are kept on this computer's Inbox, per person, so your phone and your computer show the same pins. Agents never see them. On a phone, pin from the open file: the viewer bar has the pin, and an HTML page has Pin as the first item of its full screen ⋯ menu. The Artifacts page lists this computer's threads only. #2926Filter the listA funnel icon now sits in the list header, left of Search. Its menu filters by Project (pick several; on the Inbox page, with two projects or more), Updated (Today, Last 7 days, Last 30 days or a custom range) and Agent (pick several; with two agents or more). Each row shows how many threads it would leave. Picks in one group add up (this project or that one), and different groups narrow each other. When a filter is on, the funnel turns the accent colour and shows how many picks are on. The groups in the list count only what matches, and J/K and "N new" follow the threads the filter shows. Sidebar counts don't change. When nothing matches, the list says "No threads match" with Clear filters. On a phone the menu opens as a bottom sheet. The filter is remembered in this browser only. #2921A thread's pull requestsA thread can now show the pull or merge requests its work is about. The thread's agent adds them, and you can edit the list. A row shows the state of the PR still in play (open, draft, merged or closed, in GitHub's colours) at its right end, with a small count when the thread has several. The thread header has the same mark as a button, left of Artifacts. Hover or click it for a card with each PR's state, checks and review. Stacked PRs show base first under "Stack of 3", and the others follow. On a phone, a tap opens a bottom sheet. You can add a PR by its ref or link, or remove one with Undo. A bare#123 is refused, with how to write it instead. A thread with no PRs has Add a pull request… in its ⋯ menu. Your change wakes no one: the agent hears about it the next time it wakes. The Inbox reads a PR's state only while its row or thread is on screen, keeps it for 5 minutes, and never reads a merged or closed PR again.
Agents add PRs with a new pulls field when they send a message, and list or change them with the thread_pulls action. read_thread lists them. From a terminal, use plannotator inbox pulls ls|add|rm. #2927
Choose what the sidebar showsRight-click the sidebar for Show in sidebar, a checkbox for each item that can hide. A tick changes the sidebar at once. The same menu has Customize sidebar…, a panel where you can turn items on and off, move them between the top and bottom groups, and start from Default, All at top or Minimal. Drag an item by its grip, or press the grip for Move up, Move down and Move to top or bottom. Inbox and Settings always stay. Settings → General → Appearance → Sidebar → Customize… opens the same panel, which is the way in from the keyboard or a phone. Your layout is saved in the Inbox's settings, so every window and device gets it. Reset to default puts everything back. #2924Ask AI starts from SideTo ask the agent about something it wrote, select the words in its message or in an open file and press Side in the selection bar (Copy · Delete · Comment · 👍 | Side). The thread's Ask window opens with the words quoted and the box ready to type. The agent is also told where the words came from: for a message, who sent it and the heading above the words; for a file, its name, version, line and heading. The Ask icon is gone from a thread's top bar and from a full-screen file's bar, and Ask's card in the thread's corner (the round button on a phone) is gone too. On a computer, Side opens Ask, and in a thread that already has a chat it reopens that chat. Ask isn't on phones for now. The corner still holds floating reply drafts when Settings → Experimental → Float reply drafts is on. #2928, #2987Download from a right-clickRight-click an attachment tile, the big picture at the top of a message's attachments, or a card on the Artifacts page to open its menu, with Download. The tile's ⋯ menu, now named "More", has the same list. Download saves an HTML page or a Markdown file as a file rather than opening it. For a file that was edited, it saves the file as it is now, and when the file is gone from disk the item reads "Download the sent version". An image's menu also has Copy image, and pasting that copy into a reply adds the same file. A touch never opens this menu. Pictures in a message's text keep the browser's own menu, and Save Image As now saves them under their real file name instead ofimage.png. #2923
One question mark for what waits on youList rows no longer have a separate ⚠ badge. What waits on you is the question mark with its count of open questions, and the action box for open action items. Each one fills in the existing colours: plain when nothing is held up, the Holds up colour when it is holding up work, and the Stopped colour when an agent is stopped on you. Its tooltip says which, for example "Holding up work: 5 questions". On wide lists, the words "Stopped" and "Holds up 3" stay beside it. #2929What's new: the TL;DR first, and every releaseThe What's new page now starts each release with its TL;DR, the short labelled lines at the top of these notes. A panel on the right lists the recent releases, each with its version, date and two TL;DR lines, and a row opens that release. Under 1100 px and on a phone, a version picker in the bar opens them as a sheet. The heading shows the version you have, and when you are behind, how many releases are in between. If GitHub can't be reached and nothing is saved, the page says "Can't reach GitHub" with Try again. The Inbox reads the release list at most once a day, and makes no request with update checks off. #2932Smaller changes
Pick your tab iconPlan review's Theme tab and the Inbox's Settings → General → Appearance now have a Favicon choice: Glass (the goggles, the default), Face (the goggles face from before 0.28.56) or P (a new P icon). One choice covers plan review, code review, annotate and the Inbox. In the Inbox it applies at once, with the tab's count of new threads still drawn over it. If you had picked the old face icon, you keep it, now named Face. If you had picked Classic, you get the new P icon. #2980 In 0.28.56, plan review, code review, annotate and the Inbox showed the Glass tab icon as a full square, where plannotator.ai shows it with rounded corners. Every app now uses the same favicon.ico as the site, with its hand-pixelled 16, 32 and 48 pixel frames. Face and P stay as they were. #2992Guided reviews
Not yet onThis release also carries more work on code review in the Inbox. It stays off by default, and its switch stays hidden until a later release. The work covers diagrams in the Inbox's guided reviews: a review's Mermaid diagram drawn as a picture instead of shown as source, and one optional diagram per chapter, at the top of the chapter's code #2887.Install / UpdatemacOS / Linux:
Windows:
Claude Code Plugin: The install script above also updates the plugin when claude is on your PATH. Otherwise, in a terminal:
Then restart Claude Code. Inside Claude Code, run /plugin marketplace update plannotator, then open /plugin → Installed → plannotator → Update now.
Pi:
OpenCode: Re-run the install script above. It also clears the OpenCode 2 plugin cache.
What's Changed
|
Key Features of Plannotator
Plan Review System
One of Plannotator's core capabilities is reviewing plans generated by AI agents before execution.
Developers can examine:
Proposed tasks
Implementation strategies
Agent reasoning
Planned file modifications
Workflow sequences
This visibility helps reduce unintended changes and costly mistakes.
Annotation Tools
The platform allows users to add comments, notes, and guidance directly to AI-generated plans.
These annotations can be used to:
Clarify requirements
Correct misunderstandings
Provide context
Guide future agent actions
AI Code Review
Plannotator extends the review process beyond planning by supporting inspection of generated code.
Developers can:
Review modifications
Analyze diffs
Leave comments
Request revisions
Validate implementation details
This workflow resembles modern pull-request review systems.
Human-in-the-Loop Workflows
A major design goal is ensuring that AI actions remain subject to human approval.
Organizations can establish review processes where important actions require validation before execution.
Open Source Foundation
Plannotator is open source, allowing teams to inspect, modify, and self-host the platform according to their needs.
This transparency is particularly valuable for organizations adopting AI-assisted software development.
User Experience
The interface is designed around review workflows rather than direct code generation.
Instead of interacting with a chatbot, users primarily:
Receive agent-generated plans
Review proposed actions
Add feedback
Approve or reject changes
Monitor execution results
The workflow feels familiar to developers accustomed to pull requests, code reviews, and project planning tools.
Productivity Benefits
As AI coding tools become more autonomous, review processes become increasingly important.
Plannotator helps organizations:
Reduce risky AI actions
Improve code quality
Increase accountability
Preserve architectural consistency
Encourage collaboration between developers and AI agents
For teams adopting AI-driven development, these safeguards can be as valuable as the coding agents themselves.
Collaboration Features
The platform supports collaborative review workflows where multiple team members can participate in evaluating AI-generated outputs.
This allows:
Peer review
Team approval processes
Shared annotations
Collective decision-making
Such features are especially useful for larger engineering teams.
Performance
Because Plannotator focuses on workflow management and review rather than model inference, performance largely depends on the connected AI agents and integrations.
The platform itself is lightweight and primarily serves as an orchestration and review layer.
Open Source Advantages
Being open source provides several benefits:
Transparent development
Self-hosting capabilities
Custom integrations
Community contributions
Vendor independence
Organizations concerned about compliance, security, or proprietary workflows may find these advantages particularly appealing.
Limitations
Plannotator is designed as a companion tool rather than a complete AI development platform.
Common limitations include:
Requires external AI coding agents
Best suited for teams already using AI-assisted development
Smaller ecosystem than mature developer platforms
Additional review steps may slow rapid prototyping
Some users may prefer fully autonomous workflows
The software delivers the most value in environments where oversight and quality control are priorities.
Pros
Improves transparency of AI-generated plans
Supports structured review workflows
Human-in-the-loop design
Useful annotation system
Open source
Self-hosting support
Familiar review experience for developers
Helps reduce AI-generated mistakes
Cons
Not a standalone coding agent
Requires integration with AI development tools
Smaller community than established developer platforms
Adds review overhead to workflows
Best suited for teams rather than casual users
Who Should Use Plannotator?
Plannotator is ideal for:
Software development teams
Engineering managers
AI-assisted development workflows
Organizations adopting coding agents
Open-source projects
Teams prioritizing code quality and governance
It is particularly valuable for environments where AI-generated code requires oversight before reaching production systems.
Plannotator fills an increasingly important role in the AI development ecosystem by providing visibility and control over AI-generated plans and code changes. Its focus on human oversight, structured reviews, and collaborative workflows makes it a useful companion for modern coding agents. While it is not a replacement for AI coding tools themselves, it offers a practical solution for teams seeking greater confidence and accountability in AI-assisted software development.
Developer:
backnotprop
Operating System:
Windows / macOS / Linux
Date Added:
2026-11-09T23:07:23.904Z


