Alternatives
Products that do what jj diff review integrated with agents does
https://github.com/backnotprop/plannotator
- 1
- 2
- 3DA
2014 · diffmatic.com
- 4IS
Everything that would be here is in the README. I hope this gets big, it has tons of potential.
2013 · github.com
- 5CR
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
- 6IB
I’ve spent the last 2.5 months building a product that runs LLM-powered code reviews on my pull requests — and I just launched it. The tool is built specifically for solo developers. You install it on your repo, trigger a scan by creating a pull request, and it leaves structured review comments using OpenAI under the hood. Funnily enough, I used the dev version of this app to review its own pull requests while building it. It helped me spot bugs, simplify structure, and keep quality high — all with minimal need for another human in the loop. Things I want to try out in the next months : -…
2025 · codii.dev
- 7YA
I was randomly browsing claude codes ralph wiggum plugin[1] and was surprised to see my toy project referenced. Since it appears people are getting some value out of it, thought I'd share it here... Full disclosure, this repo itself was built with a primitive ralph wiggum loop so expect AI slop. It works though. ¯\_(ツ)_/¯ https://mikeyobrien.github.io/ralph-orchestrator/ [1] https://github.com/anthropics/claude-code/tree/main/plugins/...
Dec 2025 · github.com
- 8MA
This weekend I built a multi-agent coding system which, quite unexpectedly, beat Claude Code on Stanford's Terminal Bench! The architecture is straightforward, consisting of an orchestrator agent that deploys explorer & coder subagents to complete complex terminal based tasks, utilising an intelligent context sharing mechanism along the way which makes it all work. The repo has a lot of technical details, and all the code and prompts for you to play around with if you'd like! I had a lot of fun making this, I hope you have fun reading the README, using it yourself, or even extending it! As…
2025 · github.com
- 9IB
I built a tool to roast landing pages with AI agents. I was gathering feedback from watching landing page roast videos, and figured out I could prompt LLMs to analyse a screenshot and roast based on the same criteria. It's not 100% accurate yet, but it has been really insightful when I've tested it on my own websites. Let me know what you think!
2024 · roastmylandingpage.io
- 10IB
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
- 11CP
Hi HN! I've never posted anything on here before, but this project was too fun to pass up. I've been learning a lot about agents lately, and wanted to see if I could replicate some of the results of Windsurf and Cursor. Generally I love these tools, but when you're stuck behind an "enterprise" firewall, they don't work as well. This sad state of affairs motivated me to understand SWE agents more. Does it work? Yes. Is it as good as Cursor and Windsurf? Not quite, but it's pretty darn close, depending on the model you use. I'm lacking a few features like semantic indexing, MCP support, but…
2025 · github.com
- 12BY
Hey HN - We're building wispbit (https://wispbit.com/) - a tool that lets you build your own AI code reviewer. We built this because we worked in big and complex codebases where we kept hitting booby traps - often the same ones. People forgot things, or quit altogether, amplifying the problem. We looked for other ways to fix this, but the solution is usually a combination of: - Writing a linter rule - too difficult and time consuming. - Writing docs and having frequent meetings on alignment - basically a full time job. - Using plug and play code reviewers - too generic and…
2025
- 138B
Hey all, Justin here. I previously built Phind, the AI search engine for developers. One of the biggest problems we had there was figuring out what went wrong with bad searches. We had tons of searches per day, but less than 1% of users gave any explicit feedback. So we were either manually digging through searches or making general system improvements and hoping they helped. This problem gets harder with agents. Traces are longer and more complex. It takes more effort to review them, so I'm building a tool that lets you analyze LLM outputs directly to help developers of LLM apps and agents…
Jan 2026 · trails-red.vercel.app
- 14AR
If you're interested in exploring what LLM-based agent systems these days actually do to solve certain benchmarks such as SWEBench or WebArena, we created a small leaderboard with our team, that allows to view a lot of public and OSS agent results including all the runtime traces (the step-by-step reasoning behind the scenes). Looking at traces is actually quite interesting, as they reveal a lot about the inner working and shortcomings of current agent system, e.g. see https://explorer.invariantlabs.ai/u/invariant/webarena--SteP... for an example trace.
2024 · explorer.invariantlabs.ai
- 15CA
I built this because I was tired of creating pull requests in 20 repositories just to change a single line of workflow job version. With Infra as AI, just mention the change. Agents work on all repos in parallel, read the docs, make a bunch of PRs and fill in the description. You can see the demo of the actual dashboard in the landing. Let me know your thoughts :) It means a lot to me!
Sep 2025 · infrastructureas.ai
- 16TI
Hey HN! I built AgentMGMT.dev today to keep track of all those agent orchestration tools that keep popping up. I've tried a few and landed on Superset, which I'm extremely happy (and productive!) with - but I think this category of tools will be extremely important and interesting in the next couple years, so it's worth keeping an eye on all available tools and how they evolve. I will keep the site up-to-date, please help me by submitting new tools that are not yet in the list, or add any details that might help folks who are out shopping for their first/next agent orchestrator!
May 2026 · agentmgmt.dev
- 17PA
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
- 18RA
Hi HN, I recently open sourced a small tool (Remuda) that I built at work to remove some of the friction of launching and managing agents and figured HN might be interested. I also wrote a post on the company blog that goes into more detail about why I built it and showcases its features: https://www.yendo.com/blog/remuda-an-agent-orchestrator
Jun 2026 · github.com
- 19TM
Figured I'd track the popular coding agents to see merge and approval rates. At first I was tracking Opened vs. Approved, but realized most people aren't approving; they just merge. I haven't found a way to reliably track the other agents (Jules, Devin, etc), since they don't have a standardized branch naming convention. Interesting to watch this over time. Open to ideas.
2025 · github.com
- 20IB
Fully leaned into vibe coding this time around. Started on v0, at some point ejected into running locally (getting v0's exported folder to run locally was a challenge), then iterated with Cursor over the course of a few hours. Really neat how much can be accomplished just conversationally these days.
2025 · macrodata-refinement.arjit.me
- 21AR
Hi HN. I'm the founder of Phoenix Labs (ex TikTok, Applied AI) and we're open sourcing our internal tooling today which is like a toolchain / meta-harness for CLI agents useful for really scaling eng and creative work. We are a very small team who's building a very ambitious product so we had to find ways to squeeze every ounce of efficiency that we could get our hands on. Harness strengths of different models (Claude, GPTs) and CLI-harnesses (Claude Code, Codex), safe/robust browser integration to speed up UX/QA testing, teams cli to speed up security reviews and parallelize…
May 2026 · agents-cli.sh
- 22DA
2024 · github.com
- 23IC
For the last few months I have been analysing Peter Lynch’s books on stock picking and doing prompt engineering to check if AI could create useful stock analyses. To my surprise it started making reports that allow me to understand companies much faster with well cited sources. I hope you find it interesting and useful :) Perter Lynch’s books I analyzed: Learn to earn, One up on Wall Street, Beating the street
Jun 2026 · github.com
- 24CA
TL;DR: we built a framework-agnostic agent runtime that uses gVisor for isolation and runs on k8s. It’s open-source under AGPLv3 Recently we’ve been working on a customer support “AI assistant” - essentially an interactive knowledge base/L1 support but with an option to touch resources that belong to a customer it’s talking to. We found existing tools to be lacking in these aspects: 1. Fully intercepted i/o. We wanted to trace out LLM calls as well as any other networking calls attempted by the harness so that guardrails and audit trails apply to all current and future systems…
Jul 2026 · github.com
Ranked by how close each launch is in meaning, then by votes. Refine with a description →