repowiserepowise

Command-line tool

backnotprop / plannotator

The workspace to stay in the loop and on top of agents - shape, decide, plan, annotate, review code, share with team, and send all feedback to agents with one click.

★ 14,220stars on GitHubTypeScriptApache-2.0

Claude Code, Cursor, Codex or VS Code. No key. You approve one sign-in in your browser.

Setup instructions on GitHub

Releases on GitHub (latest v0.29.1, Nov 19, 2026)

Repowise maps public repos from their source. Not affiliated with backnotprop. What is Repowise?

github.com/backnotprop/plannotatorIndexed at 5fb90d0

What is plannotator?

plannotator is a local, browser-based review surface for AI coding agents such as Claude Code, Codex, and Gemini CLI. Developers use it to annotate plans, specs, documents and code diffs, then send their feedback back to the agent. It connects to agents through plugins, hooks and commands, and its primary language is TypeScript. Its code health is 7.3 out of 10 (Good), ranked #124 of 4,000+ indexed repos. The last commit to plannotator was on Nov 17, 2026, and 180 people have contributed.

As of commit 5fb90d0, indexed Nov 17, 2026. What it is comes from a model reading the README; the rest is measured from the source and git history, not from the maintainer.

For agentsplannotator.md

Repo facts: type, license, health, rank, contributors
plannotator facts
TypeCommand-line tool
LicenseApache-2.0
Code health7.3 / 10 (Good)
Health rank#124 of 4,000+ indexed repos
Last commitNov 17, 2026
Contributors180
Bus factor1
Size6,428 files, 1,158,181 lines

Explore plannotator

Ask about this code in your agent

This connects Repowise to plannotator's code. It does not install plannotator.

Useful if you want to change or fork plannotator: your agent can ask how it is put together and get answers that cite its files.

Ask about plannotator

Answers come from plannotator's README and source, with the files they cite. Two free answers a day without an account.

Featured answer

Plannotator is a local, browser-based review surface for AI coding agents such as Claude Code, Codex, and Gemini CLI, where developers annotate plans, specs, documents and code diffs and send their feedback back to the agent. It connects to agents through plugins, hooks and commands, using agent-specific entry points such as apps/hook/server/cli.ts for hooks, apps/opencode-plugin/server.ts for OpenCode and apps/pi-extension/server.ts for Pi. When an agent proposes a plan or finishes work, the review app opens in the browser, and build/pack-app.ts packs the review, hook and inbox front ends into single HTML pages. Most of the code lives in the packages directory, including packages/inbox/App.tsx for the Inbox interface and packages/server/inbox.ts for its server side, while the bin directory holds the command-line entry point. The repository's layers by file count are UI, Application, Data, CLI, Config, Service, Utility, and Docs & Tooling, and a new reader should start with apps/hook/server/cli.ts, the packages/inbox and packages/server directories, and then build/pack-app.ts.

Files per layer in plannotator8 layers.

Basis: Inferred · knowledge graph· as of 5fb90d0

Want this for your own codebase? Map your repo free

About this page

Get a page like this for your own codebase

Repowise built this map of backnotprop/plannotator from its source and git history. It parses every symbol, draws the dependency graph, scores each file's health from complexity, duplication, coverage and churn, finds hotspots and owners in the history, and writes documentation for every module. Your coding agent reads the same index over MCP, so its answers cite real files.

Free for 2 public repos, with a page like this one. No card. See how Repowise works

Prefer local? pip install repowise && repowise init indexes your own checkout, no account needed. Star Repowise on GitHub

backnotprop/plannotator FAQ

What is plannotator?

plannotator is a local, browser-based review surface for AI coding agents such as Claude Code, Codex, Copilot CLI and Gemini CLI. It lets you annotate plans, specs, markdown, HTML and code diffs and send the feedback back to the agent.

How does plannotator work?

plannotator connects to your agent through plugins, hooks and commands. When the agent proposes a decision or plan or finishes working, the app opens in your browser so you can mark it up and send feedback to the agent to act on.

What language is plannotator written in?

plannotator is primarily written in TypeScript. The repository also contains shell, Astro, JavaScript, Python and Dockerfile files.

How is the plannotator code organized?

plannotator keeps most of its code in the packages directory, with apps holding companion packages that connect agents to the Inbox. The build directory packs front ends into single HTML pages, and tests and scripts support the test suite and releases.

When should I use plannotator?

Use plannotator when an AI coding agent proposes a plan, spec or code change and you want to review it in your browser. You can comment on the text or diff and send that feedback straight back to the agent.

What license does plannotator use?

plannotator is released under the Apache-2.0 license.

Code health

7.3out of 10Good

Hotspots average 6.0, the place fixes pay off most.

On the leaderboards:#43 of 70 TypeScript repos

Key features of plannotator

  • Annotate plans, specs, markdown, HTML and other interactive artifacts, then send the feedback to your agent.
  • Review local changes or remote PRs, comment on diffs and suggest code.
  • Code review works with Git, GitButler, Jujutsu (jj), Perforce (p4), GitHub and GitLab.
  • A guided review has an agent sort a large diff into chapters, with the important chapters first.
  • The uninstall command removes Plannotator-installed components and keeps local plans, history and settings unless purge is requested.

How backnotprop/plannotator works

Input enters through agent-specific entry points, such as apps/hook/server/cli.ts for hooks, apps/opencode-plugin/server.ts for OpenCode and apps/pi-extension/server.ts for Pi. When an agent proposes a plan or finishes work, the review app opens in the browser. The build directory packs the review, hook and inbox front ends into single HTML pages, with build/pack-app.ts supplying the review and hook builds. The packages directory holds most of the code, including packages/inbox/App.tsx for the Inbox interface and packages/server/inbox.ts for its server side. The user's annotations and comments are sent back to the agent, which acts on them. The bin directory contains the command-line entry point.

The codebase has 6,428 files and 60,653 symbols in 7 modules, led by TypeScript, Shell and Astro. Code health is 7.3 out of 10, rated good.