Read the discussion on HN. A full-thread summary is not available yet.
backnotprop
plannotator
TypeScript2025–2026
backnotprop / plannotator
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.
6Distinct people
46Mentions
1Explicit recommenders
10.2KGitHub stars
What to know before exploring
What it is
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.
GitHub
Where it is used
No documented product use was verified in the last source check.
What people are saying
Still doing https://plannotator.ai I use it daily and so do others, for - better UX, feedback, and review surfaces for ai coding agents. 1. Plan review & iterative feedback. 2.…
ramoz used a recommendation phrase. One indexed comment matches. This is a phrase match, not a verdict.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
No other repository is repeatedly linked in the same discussions.
This week on Hacker News
Nov 8–Nov 15 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/15/2026, 12:01:02 AM UTC.
Mentions over time
HN mentions by month46 dated mentions
Observed mentions: 2025-12-29 21:04:15 UTC to 2026-10-12 18:25:12 UTC.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| Dec 2025 | 2025-12-01 00:00:00 UTC | 2026-01-01 00:00:00 UTC | 5 | 2 | 3 |
| Jan 2026 | 2026-01-01 00:00:00 UTC | 2026-02-01 00:00:00 UTC | 3 | 2 | 1 |
| Feb 2026 | 2026-02-01 00:00:00 UTC | 2026-03-01 00:00:00 UTC | 9 | 2 | 7 |
| Mar 2026 | 2026-03-01 00:00:00 UTC | 2026-04-01 00:00:00 UTC | 6 | 1 | 5 |
| Apr 2026 | 2026-04-01 00:00:00 UTC | 2026-05-01 00:00:00 UTC | 6 | 1 | 5 |
| May 2026 | 2026-05-01 00:00:00 UTC | 2026-06-01 00:00:00 UTC | 6 | 1 | 5 |
| Jun 2026 | 2026-06-01 00:00:00 UTC | 2026-07-01 00:00:00 UTC | 2 | 1 | 1 |
| Jul 2026 | 2026-07-01 00:00:00 UTC | 2026-08-01 00:00:00 UTC | 2 | 2 | 0 |
| Aug 2026 | 2026-08-01 00:00:00 UTC | 2026-09-01 00:00:00 UTC | 5 | 2 | 3 |
| Sep 2026 | 2026-09-01 00:00:00 UTC | 2026-10-01 00:00:00 UTC | 0 | 0 | 0 |
| Oct 2026 | 2026-10-01 00:00:00 UTC | 2026-11-01 00:00:00 UTC | 2 | 1 | 1 |
What Hacker News says
2 sourcesRAramoz·Jul 6, 2026Submission
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 you annotate the descriptions and comments while also being able to filter bot comments.
The core tool enables focused manual review, the optional AI layer:
- Ask AI: Ask questions directly inline
- Guided Reviews: Have an agent reorganize a large diff into semantic overview sorted by importance (inspired by linear)
- Review Agents: Run review agents whose findings land as inline annotations. Review jobs can be your own skills that plannotator links to locally.
There's also a local API, your agents can POST findings or other markers/insig
Read the rest
hts/notes onto the diff. Every annotation you make is saved to ~/.plannotator. Point an agent at that history and repeated feedback distills into a custom review skill (compound engineering).
Plannotator works with most agents and the AI features utilize core model subscription providers.
Free, MIT/Apache 2.0, runs entirely on your machine.
https://github.com/backnotprop/plannotator
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 iteration loop.
Guided reviews works just like linear, except it also summarizes all file changes for you. The most important code changes are surfaced to the top, provided with a semantic overview & grouped diffs. It does not need to rely on advanced model intelligence or high reasoning efforts. Open source models work great at this task! Providers enabled include Claude Code, Codex, OpenCode, Pi, Cursor, and Copilot.
4 points · Open discussion