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, 2:17:07 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
5 sourcesRAramoz·Aug 18, 2026Submission
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 a share link with the hosted service, which I encrypt client-side and only decrypts through the link you share. The sharing service is also open source and self-hostable and open-source at https://github.com/backnotprop/plannotator
Examples:
https://guides.show/g/gs0M7zgI_zYeuqtLG4j5vQ#key=awkuPrNypYr...
https://guides.show/g/Q-ECuRlzn6I2U41wmnyVmA#key=bA52euqWQyp...
3 points · Open discussionPlannotator – Annotate plans and code reviews for agent feedback
2 points · Open discussion> On (2), I do find myself consuming agents' gigantic text responses, writing 8-bullet-point responses to guide them, then iterating that way. It's pretty exhausting. I could see inline comments providing much better ergonomics.
For your 2 plannotator [1] has a nice way to annotate agent messages or documents and its integrated into the agent chat (codex app also adopted the pattern)
[1] https://github.com/backnotprop/plannotator
In Deltahttps://github.com/backnotprop/plannotator is still very useful for annotating html prototypes and markdown plans (as well as terminal agent messages). Was glad to see codex team pick up the feature requests in the Codex App.
About to release a fun paid version. All contributors get lifetime free access.
Better running agents run longer, they need better plans. (is my bet)
In Ask HN: What are you working on? (August 2026)> The problem is defining what quality means, and providing a way for agents to optimize the harness using that lever.
I've built and my team uses plannotator [1] for specs and code review. It stores all human annotated feedback, which we compile from time-to-time and iterate on coding standard skills for automated review (that seems to get better with the more feedback we provide).
You could write a script that does the same for your PR review comments, which it sounds like you maybe do with a bit more structure.
[1] https://github.com/backnotprop/plannotator
In Harness engineering for self-improvement