Plannotator v0.24.1

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.24.1 - Software Mirrors
Plannotator v0.24.1 for Windows plannotator-paste-win32-arm64.exe | 106.86 MB plannotator-paste-win32-x64.exe | 110.08 MB plannotator-win32-arm64.exe | 160.39 MB plannotator-win32-x64.exe | 163.61 MB
Plannotator v0.24.1 for macOS plannotator-darwin-arm64 | 112.19 MB plannotator-darwin-x64 | 116.6 MB plannotator-paste-darwin-arm64 | 58.24 MB plannotator-paste-darwin-x64 | 63.07 MB
Plannotator v0.24.1 for Linux plannotator-linux-arm64 | 147.7 MB plannotator-linux-x64 | 148.23 MB plannotator-paste-linux-arm64 | 94.17 MB plannotator-paste-linux-x64 | 94.7 MB
Plannotator v0.24.1 Release Notes: Follow @plannotator on X for updates Missed recent releases? v0.24.0: PR/MR artifact gallery, GitButler review support, port ranges, expanded comment editor, OpenCode + Pi fixes v0.23.1: Startup no longer hangs on large or slow directory trees, Ask AI input stays visible after long responses v0.23.0: Plan approval fix for Claude Code 2.1.199+, annotate mode version diff, binary-only --minimal install, reviews post without attribution v0.22.0: Git-status "All changes" default review view, Commits panel with per-commit diffs, Guided Review, Pi + GitHub Copilot CLI review engines v0.21.4: Markdown math rendering, PR Overview panel with annotatable description and comments, agent instructions in code review, media parsing fixes v0.21.3: File comments in code review, unified click-to-highlight comments, VS Code clipboard/keyboard bridge, Codex Ask AI on app-server transport, CLI subcommand help v0.21.2: Custom reviews as Agent Skills, Cursor + OpenCode review engines, whole-file/general findings, deleted-annotation fix, Codex Ask AI outside git repos v0.21.1: Annotate-last blank-page fix on multi-message sessions v0.21.0: Direct document editing in annotate mode, live git-status file tree, in-app agent terminal, open files in external apps, HTML renders as HTML v0.20.3: Annotations no longer lost when clicking away, off-screen indicator for open comments v0.20.2: Pierre CodeView all-files review, large-PR pipeline and instant-open checkout, unified agent engine selection, Pi programmatic plan mode What's New in v0.24.1 A one-fix patch. plannotator annotate now opens a file you point to with a ../ path. v0.24.1 follows v0.24.0 by a few hours, so the full v0.24.0 notes are included below — most users updating now are getting both. Annotate accepts parent-relative file paths Running plannotator annotate ../docs/plan.md failed with File type not supported: .md, even though .md is supported. The path resolver rejected any relative path that pointed outside the current directory, so a ../ path never resolved. The command then found the file on disk and reported the resolver miss as a type error, which is why the message named a supported extension. An explicit path you type is now honored when the file exists, including a ../ path that points to a parent directory. This matches how absolute paths already work. Bare filenames still resolve only within the current project, so typing notes.md cannot reach a same-named file in a parent directory. Closing #1085, reported by @shulcsm. What's New in v0.24.0 This release adds two review surfaces: a gallery for the images, videos, and documents inside PR conversations, and native GitButler workspace support. 25 pull requests landed since v0.23.1. Six came from community members, four of them first-time contributors. The release also brings port ranges, an expanded comment editor, and fixes across the OpenCode and Pi integrations. PR and MR artifact gallery Pull request conversations hold more than text: screenshots of the bug, GIFs of the fix, demo videos, HTML reports, attached markdown. The review UI ignored all of it. When you review a GitHub pull request or GitLab merge request, Plannotator now collects images, GIFs, videos, HTML, and markdown files from the description and conversation into a gallery. Selecting a tile opens a focused viewer. Markdown and sandboxed HTML render inline, and everything is annotatable: select text in a document, drop a point note on an image, pin a note to a video timestamp, or comment on the artifact as a whole. These notes join your normal review feedback with their source attached, whether the feedback posts to GitHub/GitLab or returns to your local agent. Conversation artifacts sort newest-first, and you can hide tiles you don't want to see again. The gallery appears only for hosted reviews, since local diffs have no conversation to collect from. Authored by @backnotprop in #1055 GitButler review support GitButler users work in a virtual-branch workspace that ordinary Git tooling misreads: HEAD sits on a synthetic workspace commit, and several branches are applied at once. Running a code review there produced confusing diffs against internals GitButler manages for you. Plannotator now detects an active GitButler workspace and reviews it natively. The default Workspace view shows everything applied, committed changes plus assigned and unassigned working-tree changes, against GitButler's reported merge base. You can also review a single stack or one branch within a stack as committed-only diffs. Detection requires both the workspace HEAD and GitButler's local target configuration, so a leftover branch or database from a past experiment cannot hijack an ordinary Git repo. An active workspace needs the but CLI (0.21.0 or newer). --gitbutler forces the provider and --git remains the escape hatch. Both the Bun and Pi runtimes support it. The original GitButler effort came from @dansusman, whose work is preserved in the commit co-author credit. Authored by @backnotprop in #1067, superseding #566 by @dansusman Expanded comment editor in code review Long review comments were cramped in the compact inline toolbar. A new expand control opens a full-size dialog that edits the same comment, so you can draft multi-paragraph findings and submit through the familiar flow. The compact composer stays the default for quick notes and gains vertical resize. Authored by @leoreisdias in #1030 Port ranges PLANNOTATOR_PORT now accepts an inclusive range like 19432-19463. Plannotator tries each port in order and binds the first available one, in both the Bun and Pi runtimes. Fixed single ports and the random-port default behave as before. This helps devcontainer and SSH setups where you forward a block of ports and run several sessions side by side. Authored by @iurysza in #1042, their first contribution OpenCode: cancelling a plan review now cleans up Cancelling a submit_plan call in OpenCode left the review server running, so the next plan submission could not bind its port. Cancellation now flows through OpenCode's tool-abort contract: the server shuts down, timers and child processes are released, and the plan is kept so a resubmitted revision reuses the same fixed port. Authored by @backnotprop in #1064, closing #1046 reported by @fabians-px Pi: faster startup and honest error reporting The extension added about two seconds to every pi launch because its full module graph loaded at registration. The heavy browser and server graph now loads on first use, and the large UI bundles are read only when you open a review or annotate session. Separately, when a review engine failed (for example, out of API credits mid-review), Guided Review reported a generic parse failure instead of the real cause. Provider errors now surface as themselves. Authored by @backnotprop in #1063, closing #1058 reported by @tomsej, and #1061, closing #1037 reported by @alexanderkreidich Background git checks can no longer freeze the terminal Plannotator periodically checks whether your review baseline is behind its remote. On repos whose remote needs interactive authentication, that background git ls-remote could open a credential or passphrase prompt with nowhere to render. On Pi it froze the TUI. Background discovery now runs without interaction: credential prompts are disabled, SSH runs in batch mode, and timed-out processes are cleaned up as a group. Explicit actions like the "Fetch" button keep the normal interactive authentication path. Authored by @backnotprop in #1062, closing #1020 reported by @r3clin3r Workspace mode discovers symlinked repos Multi-repo workspace review walked real directories only, so a child repo reachable through a symlink was skipped. Symlinked and junction-linked repos are now discovered, deduplicated by real path, and labeled by their workspace-relative alias. This release also caps the discovery walk with the PLANNOTATOR_FILE_BROWSER_MAX_FILES budget, so a stray symlink into a huge unrelated tree cannot stall startup. Authored by @backnotprop in #1060, closing #1054 reported by @fruxxxl Additional Changes JSON 404 for unknown API routes: a nonexistent /api/* path used to return the full app HTML with a 200. All six servers (Bun and Pi) now return a JSON 404, while SPA routes still serve HTML. By @buihongduc132 in #748, their first contribution. System theme everywhere: the System option now appears in every theme menu through a shared mode list. By @gwynnnplaine in #1015. OpenCode planning handoff preserved: approving a plan with an agent switch no longer loses the planning context. By @franktronics in #1034, their first contribution. Visual-explainer Mermaid colors: the skill emitted OKLCH theme variables Mermaid cannot parse; it now emits hex. By @FNDEVVE in #1044, closing #1043, their first contribution. Review feedback validation narrowed: submitting findings no longer risks starting a second review pass. By @backnotprop in #1065. Responsive review header: the code review header now wraps at narrow widths. By @backnotprop in #1073. Open-in selector placement: the open-in-editor selector moved after the file context. By @backnotprop in #1072. 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". OpenCode: Clear cache and restart: bash rm -rf ~/.bun/install/cache/@plannotator Then in opencode.json: json { "plugin": ["@plannotator/opencode@latest"] } Pi: Install or update the extension: bash pi install npm:@plannotator/pi-extension What's Changed v0.24.1 fix(annotate): resolve explicit ../ paths that escape the project root by @backnotprop, closing #1085 v0.24.0 feat(review): add PR and MR artifact gallery by @backnotprop in #1055 Add modern GitButler review support by @backnotprop in #1067 feat(review): Add expanded review comment editor by @leoreisdias in #1030 feat(server): support bounded port ranges by @iurysza in #1042 Fix OpenCode plan cleanup after cancellation by @backnotprop in #1064 fix(review): keep background remote discovery noninteractive by @backnotprop in #1062 perf(pi): lazy-load runtime graph to cut startup time by @backnotprop in #1063 fix: surface Pi provider errors in reviews by @backnotprop in #1061 Fix workspace discovery for symlinked repositories by @backnotprop in #1060 Validate submitted findings without starting a second review by @backnotprop in #1065 fix(server): return JSON 404 for unknown /api/* routes instead of HTML by @buihongduc132 in #748 fix(review): show System in theme menu via shared mode list by @gwynnnplaine in #1015 fix(opencode): preserve planning handoff by @franktronics in #1034 fix visual-explainer Mermaid theme colors by @FNDEVVE in #1044 fix(review): make header responsive by @backnotprop in #1073 Place open-in selector after file context by @backnotprop in #1072 Refine Workspaces waitlist page by @backnotprop in #1056 Route legacy docs and blog URLs to docs.plannotator.ai by @backnotprop in #1079 docs: connect the README to canonical Plannotator docs by @backnotprop in #1080 Use the production Totman favicon by @backnotprop in #1066, #1071, and #1081 SEO: publish the new default social card by @backnotprop in #1082 Add Bing Webmaster Tools site verification by @backnotprop in #1074 chore(deps): update github actions by @renovate in #593 New Contributors @iurysza made their first contribution in #1042 @buihongduc132 made their first contribution in #748 @franktronics made their first contribution in #1034 @FNDEVVE made their first contribution in #1044 Contributors @iurysza built port range support across both server runtimes for their first contribution, with tests for the parsing edge cases. @buihongduc132's first contribution touched all six servers, giving API clients proper JSON 404s. @franktronics fixed the OpenCode planning handoff on their first PR. @FNDEVVE both reported and fixed the visual-explainer Mermaid color bug. @leoreisdias returned for a fifth contribution with the expanded comment editor. @gwynnnplaine made the System theme option consistent everywhere. @dansusman's original GitButler pull request laid the groundwork for this release's native support. Issue reporters drove much of the fix list this cycle: @shulcsm reported the parent-relative annotate failure with a clear before/after reproduction in #1085 @fabians-px reported the OpenCode cancellation port leak in #1046 @r3clin3r reported the Pi TUI freeze from background SSH prompts in #1020 @tomsej profiled and reported the 2.1s Pi startup cost in #1058 @alexanderkreidich reported Guided Review masking insufficient-credit errors in #1037 @fruxxxl reported the symlinked-repo gap in workspace mode in #1054 Full Changelog: https://github.com/backnotprop/plannotator/compare/v0.24.0...v0.24.1 (patch) · https://github.com/backnotprop/plannotator/compare/v0.23.1...v0.24.0 (v0.24.0)

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-07-20T23:02:23.862Z
Categories:

Related to Plannotator v0.24.1:

Post a Comment/Report Broken Link: