plannotator vs shippie
plannotator is much bigger: 8.4k stars against 2.5k. Over the days we have tracked them plannotator moved +41.8% and shippie +5.3%, so plannotator is growing faster right now.
shippie leads on context depth and noise control. plannotator does not take any axis by a clear margin.
Stars and commit dates come from our own daily tracking. The six axes are read off each project's documentation by our review pipeline, so they describe what a project says about itself, not what we measured in its code.
Where they stand today
A local, browser-based review surface that plugs directly into many agent hooks so you can annotate plans, diffs, and HTML and send structured feedback back to the agent.
- Stars
- 8.4k
- Tracked growth
- +41.8%
- Maturity
- ●●●●●
- Last commit
- 1d ago
- Language
- TypeScript
- License
- Apache-2.0
- Cost to run
- Free, self-hosted; external agent API keys or accounts may be required
Provides an extendable agent loop built on flue/pi with Model Context Protocol (MCP) support to explore the repo using real developer tools and integrate external tools.
- Stars
- 2.5k
- Tracked growth
- +5.3%
- Maturity
- ●●●●●
- Last commit
- 1d ago
- Language
- TypeScript
- License
- MIT
- Cost to run
- Your API key, per-PR
Six axes, head to head
Each axis runs 0 to 5. The label under a score is what that project's own docs claim, not a category average.
| Axis | plannotator | shippie |
|---|---|---|
Context depth How much of your codebase it sees before it answers: the open diff, the diff plus related files, or the whole repository. | ●●●●● Diff-focused | ●●●●● Repo exploration |
Noise control How it keeps output volume down — severity thresholds, deduplication, incremental runs over new commits only. | ●●●●● No noise controls | ●●●●● Configurable filters |
Customization How far it bends to your team: custom rules, prompts, style guides, per-path config. | ●●●●● Config file options | ●●●●● Rules & prompts |
Privacy Whether your code stays on your own infrastructure: fully local, self-hostable, or cloud API only. | ●●●●● Self-hostable | ●●●●● API-key cloud |
Model freedom Whether you can point it at any provider, or it is wired to one. | ●●●●● Multiple providers | ●●●●● Multiple providers |
Setup ease What it takes to get a first useful run out of it. | ●●●●● One-command install | ●●●●● Quick start |
Which one to pick
Pick plannotator if…
Local and agent-integrated: pick Plannotator when you want a local browser UI to review agent plans and code diffs and to send feedback directly to the agent.
Pick shippie if…
Extensible — pick Shippie when you want a provider-agnostic, extendable code-review workflow that can run locally or in CI and integrate external tools via MCP.
- Context depth: Repo exploration (4/5 against 2/5)
- Noise control: Configurable filters (3/5 against 1/5)
What people want from each one
backnotprop/plannotator
mattzcarey/shippie
Questions people ask
Is plannotator better than shippie?
shippie leads on context depth and noise control. plannotator does not take any axis by a clear margin. plannotator is worth picking when local and agent-integrated: pick Plannotator when you want a local browser UI to review agent plans and code diffs and to send feedback directly to the agent.
Which of plannotator and shippie keeps my code private?
plannotator: Self-hostable (4/5). shippie: API-key cloud (3/5).
What does each one cost to run?
plannotator: Free, self-hosted; external agent API keys or accounts may be required. shippie: Your API key, per-PR.
Full profiles: backnotprop/plannotator and mattzcarey/shippie. Everything else in Code review agents.