Alternatives
Products that do what Plannotator does
Annotate, review, and share Claude Code plans. (Plugin/Hook)
- 1
- 2
- 3PA
I started this in January as a hook for Claude Code's plan mode: when it finished planning, instead of approving a wall of text in the terminal, the plan opens in your browser and you could mark it up like a document. Your annotations go back into the agent session. It grew from there. There's now PR-style code review (git, jj, p4, GitHub/GitLab PRs) and annotation for markdown, URLs, and folders. Agents produce a lot of HTML now, so Plannotator renders those artifacts and lets you annotate them too. Nine harnesses are supported: Claude Code, Codex, Copilot CLI, Gemini, OpenCode, Kiro,…
Jun 2026 · github.com
- 4
- 5
- 6
- 7
- 8
- 9
- 10
- 11
- 12AP
I've been working on this internal project initially both to learn more Vibe-Coding but also to help our teams and projects to use AI more efficiently. As more people used it, it grew to support multiple teams/projects to analyze their Claude Code conversation and optimize them over time (understanding how to write better conversation with Claude Code and share knowledge between them) With time we added support for multiple Claude account management and monitor usage/rate limit. This is a simple project but has proved to be quite useful for our company. We have reached 5000+…
2025 · github.com
- 13TT
I built two CLI tools to fix friction points with Claude Code: claude-remote-approver – Sends permission prompts (Bash, Write, Edit) as push notifications to your phone via ntfy.sh. Tap Approve/Deny from anywhere. Falls back to terminal on timeout. Supports "Always Approve" for trusted tools. claude-plan-reviewer – Hooks into Claude Code's plan mode and sends plans to a rival AI (OpenAI Codex CLI or Gemini CLI) for review. Feedback gets injected back, Claude revises, repeats for N rounds. Different models catch different blind spots. Together: give Claude a task, walk away, rival AI…
Mar 2026
- 14CR
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…
Jul 2026 · plannotator.ai
- 15CC
Uses agent and Git Hooks to automatically create Git Notes on commit, containing the agent conversation that led to that commit. Works if either you or the agent commit. It's basically the same thing as entire.io just announced that they got $60m investment for. Except I got Claude Code to write it last week, in my spare time, without really paying attention. I certainly didn't read or write any of the code, except for one rubbish joke in the README. I've got a Claude Code instance working on Gemini CLI support and OpenCode support currently.
Feb 2026 · github.com
- 16CR
Hey HN, Over the past 10 months I've been using Claude Code heavily, and one limitation kept coming up: you can really only run one coding agent at a time. While one agent is refactoring something, the rest of the repo is basically blocked unless you start manually juggling branches and working directories. The core issue is that AI coding agents operate directly in your filesystem. If two agents run in the same working directory they quickly start stepping on each other’s changes. Git worktrees turned out to be a surprisingly good primitive for solving this. So I built ChatML, a Desktop app…
Mar 2026 · github.com
- 17
- 18JD
https://github.com/backnotprop/plannotator
May 2026 · twitter.com
- 19RC
The magic in AI coding assistants isn't the code -- it's the prompts. I studied the externally observable behavior of Claude Code and recreated it from scratch in Python with the exact same behaviors. It works with any model -- OpenAI, Gemini, Claude. What's surprising: 1. You can keep the core agent really simple, just 280 lines of Python. As long as it supports hooks, custom sub-agents and Model Context Protocol (MCP), then all the rest of the coding-assistant-specific behavior and tools can be factored out into a separate MCP server. 2. The magic is in the prompts (1200 lines of…
2025 · github.com
- 20CM
I built an MCP server that connects coding agents (Claude Code, Cursor, OpenCode, Codex) to a collaborative workspace where your team and other AI models can review what the agent is planning. The problem: When Claude Code creates an implementation plan, it lives in your terminal session. Nobody else sees it until it becomes a PR. If you want GPT to check the architecture or a teammate to flag issues, you're copy-pasting between windows. This MCP server fixes that. When your agent creates a plan, it gets shared as a collaborative thread in CoChat. Engineers comment on it, other AI models…
Feb 2026 · github.com
- 21SR
Hello all, I'm a software developer. Over the last few months more and more of my work has turned into using coding agents instead of typing the whole code myself. Usually a few claude sessions at once, sometimes codex, one per feature or per revealed bug. I ran them in a split terminal for a few weeks, and quickly spotted two main problems. The first is that I couldn't easily tell which agent was stuck waiting on me and which was still working, so I'd cycle through sessions and checking on them. The second one: agents sharing a single branch step on each other. Two of them could be editing…
Jul 2026 · shikigami.dev
- 22AF
Hey HN, Claude Code is powerful, but its execution is a black box. You see the final result, not the journey. Agent Flow makes the invisible visible in realtime: - Understand agent behavior: See how Claude breaks down problems, which tools it reaches for, and how subagents coordinate - Debug tool call chains: When something goes wrong, trace the exact sequence of decisions and tool calls that led there - See where time is spent: Identify slow tool calls, unnecessary branching, or redundant work at a glance - Learn by watching: Build intuition for how to write better prompts by observing how…
Mar 2026 · github.com
- 23AC
When AI coding tools help you plan a project, they describe your options in text and ask you to pick. That works fine for technical choices but falls apart for anything visual. "A sticky navbar with a hamburger menu" vs "a sidebar with collapsible sections" is hard to evaluate without seeing them. I built a Claude Code skill that generates a self-contained HTML page for each decision point and opens it in the browser. Each page has four options with visual previews (rendered CSS mockups for UI decisions, flow diagrams for interactions, architecture diagrams for technical choices), a…
Mar 2026 · github.com
- 24IB
The main goal of this was to be able to not just run multiple Claude Code sessions at once, but actually manage them and keep track of what I was doing. Sometimes this is multiple attempts on the same task, sometimes I work several tasks at once. Really I was just sick of twiddling my thumbs waiting for the coding agent to finish, and I wanted it to be easy to work on/review/test another change while I waited.
2025 · github.com
Ranked by how close each launch is in meaning, then by votes. Refine with a description →