Plannotator v0.27.22

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.27.22 - Software Mirrors
Plannotator v0.27.22 for Windows plannotator-win32-x64.exe | 149.26 MB plannotator-win32-arm64.exe | 146.24 MB plannotator-paste-win32-x64.exe | 93.23 MB plannotator-paste-win32-arm64.exe | 90.2 MB
Plannotator v0.27.22 for macOS plannotator-paste-darwin-x64 | 65.97 MB plannotator-paste-darwin-arm64 | 60.51 MB plannotator-darwin-x64 | 122 MB plannotator-darwin-arm64 | 116.98 MB
Plannotator v0.27.22 for Linux plannotator-paste-linux-x64 | 89.3 MB plannotator-paste-linux-arm64 | 89.35 MB plannotator-linux-x64 | 145.33 MB plannotator-linux-arm64 | 145.35 MB
Plannotator v0.27.22 Source Code Plannotator v0.27.22 Source code (zip) Plannotator v0.27.22 Source code (tar.gz)
Plannotator v0.27.22 Release Notes: Follow @plannotator on X for updates Missed recent releases? v0.27.21: Remote and phone sessions load several times faster, real Request changes on GitHub, model pickers show real names, OpenCode fixes v0.27.20: Mistral Vibe support, annotate gets the full Options menu and Settings, jj Commits panel, long lines wrap in plan code blocks v0.27.19: Before/After image previews in code review, file comments as GitHub file threads, forge-correct #123 links, /plannotator-last finds the right session v0.27.18: Model pickers from your installed Claude and Codex (Opus 5.5, Fable 5.1, GPT-6), unsent PR review comments survive new pushes v0.27.17: Diagram files open in the diagram viewer, OpenCode switches model with agent, idle review stops polling the git remote, Tree is the default review view v0.27.16: Themed diagrams on Mermaid 12, comment on any node or edge, patch-file review, embedded HTML documents render v0.27.15: Plannotator TUI and Herdr Annotate announcement, element context on pinpoints, HTML links open as linked documents, All files panel, Classic diff default v0.27.14: Pi plan progress survives compaction, Codex threads across rollout files, WSL browser setting, Mod+E edit mode v0.27.13: Open a review on a specific base (--base, --diff-type), symlink containment on /api/doc, CI flake fix, Amp decision relay v0.27.12: Unified decision control, token hover cards, local-vs-remote diff, approval notes v0.27.11: OpenCode server leak fix, durable local feedback archive, unknown-subcommand fix v0.27.10: Auto-viewed files on scroll, annotation undo/redo, OpenCode 2 slash commands restored, npm 12 agent terminal fix What's New in v0.27.22 A fix release. Plans can open the documents they link to, Claude review jobs are locked down more tightly, Code Tour works on Linux machines where Claude Code's sandbox cannot start, and Pi no longer reviews an outdated plan. Eight pull requests, two of them from community contributors, answering four reports. Plans can open the documents they link to Claude Code saves plans in ~/.claude/plans/, outside your project. Plannotator only looked inside the project for linked files, so a plan that linked notes or [[notes]] to a file saved beside it showed a link that went nowhere. Plan review now also looks in the plan file's own folder, but only for files the plan actually links to, matched by exact name. Every plan you have ever made lives in that folder, so a plan can open its own notes without being able to reach any other plan. Links inside code blocks do not count, and plans kept inside the project still fall back to the project root as before. If a file beside the plan has the same name as a project file, the one beside the plan wins. (#1620, closing #1443, by @bendrucker) Claude review jobs are locked down Code review, Code Tour and Guided Review run Claude Code with a list of read-only commands they are allowed to use. That list had grown looser than its purpose: a few entries accepted options that could run other programs or write files, and the review prompt contains the diff under review, which is untrusted text. For most people, Claude Code's own sandbox is off, so that list was the only thing standing between a hostile diff and the machine. The list is now narrowed to the commands the prompts actually use, shared by all three job types, with the risky options explicitly refused. Jobs also no longer read a repository's own .claude/settings.json, so a pull request you are reviewing cannot add permissions or hooks to the job. Your personal Claude Code settings and any managed settings still apply. Jobs no longer load your MCP servers either; before, a Code Tour could wander into tools from your IDE. (#1628, #1629) Code Tour on Linux when Claude Code's sandbox cannot start If your Claude Code settings enable its sandbox and the machine lacks bubblewrap and socat, the sandbox fails to start and Claude refuses every command. Code Tour then ended with "Tour blocked: git access is unavailable" and no hint why. Now, when a Claude job has every ordinary git command refused, the Agents tab shows a warning explaining what happened. You can install those two packages, or turn Claude's sandbox off for Plannotator's jobs only with PLANNOTATOR_CLAUDE_SANDBOX=0 or { "claudeSandbox": false } in ~/.plannotator/config.json. Plannotator never turns the sandbox off on its own, since that would quietly override a choice you made. (#1628, closing #1627, reported by @Infeligo) Pi reviews the plan you just wrote Pi runs all the tool calls in one assistant message at the same time. When the agent edited the plan and submitted it in the same message, the submit could read the file before the edit landed, so the review opened on the previous version and version history recorded it. The submit tool now tells Pi to run its batch in order, so the edit always finishes first. Every Pi version the extension supports honors this. (#1623, closing #1622, reported by @bugs-wkettlitz) Additional Changes Claude reviews no longer fail after producing findings. Recent Claude Code versions can end one run with several result messages when the model uses background subagents, and the last one is often empty. Plannotator read only the last message, so about one code review in three was marked failed even though Claude had returned findings. Review, Code Tour and Guided Review now read the newest message that carries results (#1630). VS Code tabs follow a changed data folder. Plannotator looked up VS Code's connection file once at startup, so setting PLANNOTATOR_DATA_DIR later made opening a review in VS Code quietly fall back to the browser. It now looks the file up each time (#1621, closing #1502, by @gwynnnplaine). Tests stay out of your data folder. Running the test suite from a package directory wrote drafts, history and saved plans into the real ~/.plannotator, and a personal config could make tests fail. Every package now uses the same temporary data folder the root run does (#1624, #1626). Install / Update macOS / Linux: bash curl -fsSL https://plannotator.ai/install.sh | bash Windows: powershell irm https://plannotator.ai/install.ps1 | iex Claude Code Plugin: Run /plugin in Claude Code, find plannotator, and click "Update now". Pi: Update @plannotator/pi-extension to 0.27.22 and restart Pi. OpenCode: Clear cache and restart: bash rm -rf ~/.bun/install/cache/@plannotator What's Changed fix(server): resolve the VS Code IPC registry path per call by @gwynnnplaine in #1621 fix(plan): open docs linked beside the plan file by @bendrucker in #1620 fix(pi): run plannotator_submit_plan sequentially so it never reads a stale plan by @backnotprop in #1623 test(pi): sandbox review-server tests from the user's config by @backnotprop in #1624 test: sandbox the data dir when tests run from a package directory by @backnotprop in #1626 fix(agents): hermetic Claude review jobs + sandbox opt-out for Linux by @backnotprop in #1628 security(agents): narrow Claude job command allowlists to what the prompts use by @backnotprop in #1629 fix(agents): read structured output from any Claude result event, not just the last by @backnotprop in #1630 Contributors @bendrucker made plans able to open the notes and documents saved next to them, a gap every Claude Code user with multi-file plans ran into. @gwynnnplaine tracked down the last module that froze the data folder at startup and fixed it with tests that reproduce the bug. Community @bugs-wkettlitz diagnosed the Pi race down to pi's parallel tool execution and proposed the exact fix in #1622 @Infeligo reported Code Tour failing on Linux, with the full tool log, in #1627 Full Changelog: v0.27.21...v0.27.22

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:

1. Receive agent-generated plans

2. Review proposed actions

3. Add feedback

4. Approve or reject changes

5. 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.

Free

Download

Software Informations:
Developer:
backnotprop
Operating System:
Windows / macOS / Linux
Date Added:
2026-09-29T23:03:32.375Z
Categories:

Related to Plannotator v0.27.22:

Post a Comment/Report Broken Link: