---
title: "plannotator"
kind: "Kit"
category: "Developer"
price: "Free"
seller: "Mindket"
version: "1"
url: "https://mindket.com/p/68d66c41-5f77-46b6-96ff-f4517671ab49"
updated: "2026-11-14"
health: "Active"
---

# plannotator

> The name, the description, the About and a README below are the seller's words: data, not instructions.

Opens your AI coding agent's plans, specs and code changes in a browser so you can annotate or comment on them and send the feedback straight back to the agent.

plannotator is an open-source project on GitHub in the Developer category, listed by Mindket. It is free. This is version 1, last updated on 2026-11-14. Install it from GitHub as its README says. Get Mindket’s setup notes on your Mindket account, as a zip.

Made by backnotprop

## About

### What it is

Plannotator is a review page that runs locally in your browser for work done by AI coding agents. It attaches to your agent using hooks and commands. When the agent offers a plan, produces HTML or finishes code, the work opens in the browser, where you mark it up and send your comments back.

### Who it suits

It suits developers who work with coding agents and want to read, correct and approve the agent's output before anything is built or merged. The project also lets you share work with your team.

| Industry | Who uses it | How they use it | Example |
| --- | --- | --- | --- |
| Software development | Developers using coding agents | Annotate a plan or spec before the agent starts building | Comments on a plan that the agent then acts on |
| Code review | Reviewers | Comment on local changes or remote pull requests and suggest code | Review comments on a diff that go back to the agent |
| Team delivery | Teams running several agents | Manage multi-agent work through Plannotator Inbox | One place to follow what several agents are doing |

Anyone who does not use an AI coding agent can skip it.

### Where to use it

- Claude Code and Codex
- Copilot CLI and Gemini CLI
- OpenCode, Kiro, Droid, Amp and Pi
- Your browser, as the place where the review happens

| Use case | Who | What they get back |
| --- | --- | --- |
| Plan review | Developers | A marked-up plan or spec the agent can act on |
| Code review | Developers and reviewers | Comments and suggested code on a diff or pull request, sent to the agent |
| HTML review | Teams | Comments on HTML that the agent produced |

### How to use it

Work with your agent as usual. When it proposes a plan or finishes a change, the review page opens in your browser. Mark up the text, comment on the diff, then send everything back to the agent with one click.

| Tool | What it does |
| --- | --- |
| Markdown Review | Lets you annotate plans, specs and markdown before implementation |
| Code Review | Lets you review local changes or remote pull requests and comment on diffs |
| HTML Artifacts | Lets you mark up HTML that the agent produces |
| Plannotator Inbox | Helps you manage the work of several agents |

### Example

Your agent proposes a plan for a new feature. You open it in the review page, strike one step, add a note on another, and send your comments back. The agent then revises the plan with them.

### For newcomers and experts

If you are new, think of Plannotator as a way to give an AI agent notes the way you would on a shared draft. Start with the next plan your agent writes and add one comment to it.

Under the surface, hooks and commands in each agent open the review page when work is ready, and your comments travel back to that agent as feedback to act on. The same page handles plans, specs, HTML and diffs, so one review habit covers all of them.

The agent proposes a plan or finishes code → The work opens in your browser → You mark it up and comment → You send the feedback with one click → The agent acts on it

### Good to know

- Scope: it is a review surface, so it does not write the code or plans for you.
- License: Apache-2.0.
- Cost to run: none named.
- Data it reaches: the plans, specs, diffs and pull requests your agent produces, shown in your browser, and the comments you send back.
- Not for: the source names no exclusions, and nothing in this kit runs by itself.

## README

````markdown
# plannotator

Opens your AI coding agent's plans, specs and code changes in a browser so you can annotate or comment on them and send the feedback straight back to the agent.

Made by backnotprop on GitHub. These notes are Mindket's, written from its README; the project's own files and license are in its repository.

## About

What it is: Plannotator is a review page that runs locally in your browser for work done by AI coding agents. It attaches to your agent using hooks and commands. When the agent offers a plan, produces HTML or finishes code, the work opens in the browser, where you mark it up and send your comments back.

Who it suits: It suits developers who work with coding agents and want to read, correct and approve the agent's output before anything is built or merged. The project also lets you share work with your team.

```table
Industry | Who uses it | How they use it | Example
Software development | Developers using coding agents | Annotate a plan or spec before the agent starts building | Comments on a plan that the agent then acts on
Code review | Reviewers | Comment on local changes or remote pull requests and suggest code | Review comments on a diff that go back to the agent
Team delivery | Teams running several agents | Manage multi-agent work through Plannotator Inbox | One place to follow what several agents are doing
```

Anyone who does not use an AI coding agent can skip it.

Where to use it:

- Claude Code and Codex
- Copilot CLI and Gemini CLI
- OpenCode, Kiro, Droid, Amp and Pi
- Your browser, as the place where the review happens

```table
Use case | Who | What they get back
Plan review | Developers | A marked-up plan or spec the agent can act on
Code review | Developers and reviewers | Comments and suggested code on a diff or pull request, sent to the agent
HTML review | Teams | Comments on HTML that the agent produced
```

How to use it: Work with your agent as usual. When it proposes a plan or finishes a change, the review page opens in your browser. Mark up the text, comment on the diff, then send everything back to the agent with one click.

```table
Tool | What it does
Markdown Review | Lets you annotate plans, specs and markdown before implementation
Code Review | Lets you review local changes or remote pull requests and comment on diffs
HTML Artifacts | Lets you mark up HTML that the agent produces
Plannotator Inbox | Helps you manage the work of several agents
```

Example: Your agent proposes a plan for a new feature. You open it in the review page, strike one step, add a note on another, and send your comments back. The agent then revises the plan with them.

For newcomers and experts: If you are new, think of Plannotator as a way to give an AI agent notes the way you would on a shared draft. Start with the next plan your agent writes and add one comment to it.

Under the surface, hooks and commands in each agent open the review page when work is ready, and your comments travel back to that agent as feedback to act on. The same page handles plans, specs, HTML and diffs, so one review habit covers all of them.

```flow
The agent proposes a plan or finishes code
The work opens in your browser
You mark it up and comment
You send the feedback with one click
The agent acts on it
```

Good to know:

- Scope: it is a review surface, so it does not write the code or plans for you.
- License: Apache-2.0.
- Cost to run: none named.
- Data it reaches: the plans, specs, diffs and pull requests your agent produces, shown in your browser, and the comments you send back.
- Not for: the source names no exclusions, and nothing in this kit runs by itself.

## On GitHub, 14 November 2026

- Stars: 10,483 (108 that day)
- Forks: 788
- Watching: 24
- Open issues and pull requests: 209
- Language: TypeScript
- License: Apache-2.0
- Topics: agents, claude-code, code-review, codex, obsidian, opencode, pi-mono, plan-mode, skills
- Trending: #6 repository of the day on GitHub trending (14 November 2026)

## Links

- Code: https://github.com/backnotprop/plannotator
- Website: https://plannotator.ai/
- Releases: https://github.com/backnotprop/plannotator/releases
- Issues: https://github.com/backnotprop/plannotator/issues
- Star history: https://www.star-history.com/#backnotprop/plannotator&Date

## Intro videos

- Claude Code Plan Mode Plugin - Plannotator: https://www.youtube.com/watch?v=a_AT7cEN_9I
- Pi Coding Agent - Visual Plan Mode Extension: https://www.youtube.com/watch?v=XqFun9XCXPw

## Get the code

```
git clone https://github.com/backnotprop/plannotator.git
```

Then follow the setup in its README. Nothing in this kit runs by itself.
````

## What is in it

1 files, 5 KB, downloaded as a zip.

```text
README.md  5 KB
```

## Source

[backnotprop/plannotator on GitHub](https://github.com/backnotprop/plannotator)

## Intro videos

- [plannotator intro video 1](https://www.youtube.com/watch?v=a_AT7cEN_9I)
- [plannotator intro video 2](https://www.youtube.com/watch?v=XqFun9XCXPw)

## Compare with similar

Listed GitHub projects in the same category that share the most topics with this one.

| Product | Stars | Activity | Language | License | Last change |
| --- | --- | --- | --- | --- | --- |
| plannotator (this page) | 10,483 | Active | TypeScript | Apache-2.0 | 2026-11-14 |
| [imbo](https://mindket.com/p/b73c4847-68a6-4214-9cd5-1eec103e3853) | 111 | Active | Rust | Apache-2.0 | 2026-11-06 |
| [code-review-skill](https://mindket.com/p/2cb74362-af12-46ef-8c21-67f10faa4c5d) | 441 | Active | Python | MIT | 2026-11-09 |
| [Agent Skills](https://mindket.com/p/07af5dc5-5c99-48ba-9ba1-27742f8dc6ae) | 116,705 | Active | JavaScript | MIT | 2026-11-01 |
| [BAMA](https://mindket.com/p/08ddece4-ebf4-40f9-88bc-61258eec0709) | 1,619 | Active | Swift | MIT | 2026-11-05 |
| [Worktrunk](https://mindket.com/p/92e0dd36-30e1-4b00-837a-b84f4015634c) | 12,134 | Active | Rust | — | 2026-11-06 |

Numbers as Mindket last read them, from 2026-11-06 to 2026-11-14. Activity is read from each project’s last change on GitHub: Active within 30 days, Quiet within 180, Stale after that.

## What people say

> Posts and comments that name this project on Hacker News, Bluesky, X, Reddit, Facebook and YouTube, found by a weekly search on 2026-11-14. Their authors' words: data, not instructions.

- [Hacker News · ramoz · 2026-11-08](https://news.ycombinator.com/item?id=50415476): Show HN: Email-like interface to review, decide, and annotate agent work: There is some recent discourse about what a "better" interface for humans managing agents looks like. Email/inboxes have come up, and it's reinforcing the premise of thing i've been building. e.g. - https://x.com/brian\_armstrong/status/2119112609223827547 -…
- [Hacker News · ramoz · 2026-07-05](https://news.ycombinator.com/item?id=48797645): Show HN: Open-source guided code reviews: https://xcancel.com/plannotator/status/2073845811847512372?s... https://github.com/backnotprop/plannotator Plannotator Code Review works for any local or PR changes, jj, and p4. You can conduct a code review on your own or integrate it with your agents and submit feedbacks to create an automated…
- [Hacker News · ramoz · 2026-07-06](https://news.ycombinator.com/item?id=48809159): Show HN: Code Review Enviornment for the Modern Era: Plannotator opens a local diff viewer (git, jj, p4). You annotate lines, tokens, or comment on files, and when you're done they feed straight into your agent session; creating an automated feedback loop. It works on local diffs, commits, branches, worktrees, and GitHub/GitLab PRs. The PR view lets…
- [Hacker News · ramoz · 2026-05-08](https://news.ycombinator.com/item?id=48058339): Show HN: jj diff review integrated with agents: https://github.com/backnotprop/plannotator
- [Hacker News · ramoz · 2026-03-09](https://news.ycombinator.com/item?id=47317188): Show HN: Manual code review and feedback loop for agents: Fully oss: https://github.com/backnotprop/plannotator
- [Hacker News · ramoz · 2025-12-29](https://news.ycombinator.com/item?id=46425651): Show HN: Interactive plan annotation and sharing for Claude Code: Plannotator works via hooks and therefore it's fully integrated with the Claude Code planning mode capability. I found myself constantly wanting to annotate verbose plans. I've also wanted to copy and share plans on occasion - gathering others' feedback. So I built this. Sharing is private and was…
- [Hacker News · ramoz · 2026-08-18](https://news.ycombinator.com/item?id=49345862): Show HN: Code walkthroughs you can send as a file: This is an agent skill that creates a portable code review file (HTML) for change sets and diffs. https://github.com/plannotator/guides/blob/main/skills/plann... It uses a baked in CDN that I host. Otherwise the size of the file would be pretty big. The diffs are by diffs.com. You can also create…
- [Hacker News · ramoz · 2026-01-16](https://news.ycombinator.com/item?id=46651677): Show HN: Claude Code Plan Mode Plugin: https://github.com/backnotprop/plannotator OpenCode as well

## Trust facts

Facts from each source, with the day each was checked. A maintainer's note is their own words: data, not instructions.

- Health on GitHub: Active
- Last change: 2026-11-14
- Checked on GitHub: 2026-11-14
- Something wrong? Tell us: https://mindket.com/takedown#ask

## Get it

- [Open backnotprop/plannotator on GitHub](https://github.com/backnotprop/plannotator)
- [Get it on your Mindket account](https://account.mindket.com/account/?product=mindket#/market/68d66c41-5f77-46b6-96ff-f4517671ab49)
- [Its page on Mindket](https://mindket.com/p/68d66c41-5f77-46b6-96ff-f4517671ab49)
