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
6 sourcesRAramoz·Mar 15, 2026
Right now I enjoy the labs' cli harnesses, Claude Code, and Codex (especially for review). I do a bunch of niche stuff with Pi and OpenCode. My productivity is up. Some nuances with working with others using the same AI tools- we all end up trying to boil the ocean at first- creating a ton of verbose docs and massive PRs, but I/they end up regressing on throwing up every sort of LLM output we get. Instead, we continously refine the outputs in a consumable+trusted way.
My workday is fairly simple. I spend all day planning and reviewing.
1. For most features, unless it's small things, I will enter plan mode.
2. We will iterate on planning. I built a tool for this, and it seems that this is a fairly desired workflow, given the popularity through organic growth. https://github.com/backnotprop/plannotator
- This is a very simple tool that ca
Read the rest
ptures the plan through a hook (ExitPlanMode) and creates a UI for me to actually read the plan and annotate, with qol things like viewing plan diffs so I can see what the agent changed.
3. After plan's approved, we hit eventual review of implementation. I'll use AI reviewers, but I will also manually review using the same tool so that I can create annotations and iterate through a feedback loop with the agents.
4. Do a lot of this / multitasking with worktrees now.
Worktrees weren't something I truly understood the value of for a while, until a couple weeks ago, embarrassingly enough: https://backnotprop.com/blog/simplifying-git-worktrees/
Well, your best bet is some type of hook that can just reject ExitPlanMode and remind Claude that he's to stay in plan.
You can use `PreToolUse` for ExitPlanMode or `PermissionRequest` for ExitPlanMode.
Just vibe code a little toggle that says "Stay in plan mode" for whatever desktop you're using. And the hook will always seek to understand if you're there or not.
- You can even use additional hooks to continuously remind Claude that it's in long-term planning mode.
*Shameless plug. This is actually a good idea, and I'm already fairly hooked into the planning life cycle. I think I'll enable this type of switch in my tool. https://github.com/backnotprop/plannotator
In Shall I implement it? NoShow HN: Manual code review and feedback loop for agents
Fully oss: https://github.com/backnotprop/plannotator
4 points · Open discussionSide project - plan mode and code review annotations for coding agents (ui that integrates via hooks):
https://github.com/backnotprop/plannotator
Main gig:
Trusted agents. We just shipped hardware based signing to web bot auth protocol.
In Ask HN: What Are You Working On? (March 2026)> Claude Code style plan mode to be a bit restrictive
Hey thats why i built plannotator: https://github.com/backnotprop/plannotator
I like staying within Claude Code for orchestrating its plan mode, but I needed a better way to actually review the plan, address certain parts, see plan diffs, etc all in a better visual way. The hooks system through permissionrequest:exitplanmode keep this fairly ergonomic.
see it in action: https://www.youtube.com/watch?v=a_AT7cEN_9I
In LLMs work best when the user defines their acceptance criteria firstI did a sort of bell curve with this type of workflow over summer.
- Base Claude Code (released)
- Extensive, self-orchestrated, local specs & documentation; ie waterfall for many features/longer term project goals (summer)
- Base Claude Code (today)
Claude Code is getting better at orchestrating it's own subagents for divide/conquer type work.
My problem with these extensive self-orchestrated multi-agent / spec modes is the type of drift and rot of all the changes and then integrated parts of an application that a lot of the time end up in merge conflicts. Aside from my own decision cognitive space, it's also a lot to just generally orchestrate and review. I spent a ton of type enforcing Claude to use the system I put in place including documentation updates and continuous logging of work.
I feel extremely productive with a single Claude
Read the rest
Code for a project. Maybe for minor features, I'll launch Claude Code in the web so that it can operate in an isolated space to knock them out and create a PR.
I will plan and annotate extensively for large features, but not many features or broad project specs all at the same time. Annotation and better planning UX, I think, are going to be increasingly important for now. The only augment of Claude Code I have is a hook for plan mode review: https://github.com/backnotprop/plannotator