Alternatives
Products that do what Revibe — Your codebase, fully understood does
Helping Agents and Human Orchesterators read the same notes.
- 1
- 2
- 3GF
hi guys. been working on something i think is fundamentally missing in today's workflow with ai agents. vcs. i find myself struggling with questions that agents can't answer like "why did you do it?", "when did u delete this folder? why?", etc. or trying to /rewind (after a /compact...) or basically `bisect` to find when and why something was done by the agent in the current / previous session. just like git did for code, i think we are the same core capabilities with ai agents so... i developed an open source solution for that (currently supporting claude code) would love to…
May 2026 · github.com
- 4
- 5
Deep Work Plan▲114Models matter. Context matters more. Give your agent a plan.
Jun 2026 · deepworkplan.com
- 6
- 7
- 8
- 9RA
I started building this 10 months ago, largely using agentic coding tools. I've stayed very involved in the code base and architecture, and have never moved faster in my life as a dev. The word processor engine and rendering layer are all built from scratch - the only 3rd party library I used was the excellent Y.js for the CRDT stack. Would love some feedback!
Mar 2026 · revise.io
- 10
- 11DT
Hi HN, We are researchers from ETH Zurich interested in the real-world adoption and impact of Code Agents. To measure this, we built a dashboard, scraping all public PRs on GitHub, analyzing which are created by different code agents (Codex, Jules, Copilot, Devin, etc.), and measuring their merge rates, sliced by various repository and PR characteristics. https://insights.logicstar.ai Since mid-May, we've analyzed over 10 million PRs and already found some interesting trends: Usage is high, but shallow. Agents submit ~7% of all PRs overall, but only ~1–2% on popular repos. Most…
2025 · github.com
- 12RT
This project (Agents Observe) started as an exploration into building automation harnesses around claude code. I needed a way to see exactly what teams of agents were doing in realtime and to filter and search their output. A few interesting learnings from building and using this: - Claude code hooks are blocking - performance degrades rapidly if you have a lot of plugins that use hooks - Hooks provide a lot more useful info than OTEL data - Claude's jsonl files provide the full picture - Lifecycle management of MCP processes started by plugins is a bit kludgy at best The biggest takeaway is…
Apr 2026 · github.com
- 132C
Single-agent LLMs suck at long-running complex tasks. We’ve open-sourced a multi-agent orchestrator that we’ve been using to handle long-running LLM tasks. We found that single LLM agents tend to stall, loop, or generate non-compiling code, so we built a harness for agents to coordinate over shared context while work is in progress. How it works: 1. Orchestrator agent that manages task decomposition 2. Sub-agents for parallel work 3. Subscriptions to task state and progress 4. Real-time sharing of intermediate discoveries between agents We tested this on a Putnam-level math problem, but the…
Feb 2026 · github.com
- 14
- 15
- 16CS
We now write most of our code with agents. For a while, PRs piled up, causing review fatigue, and we had this sinking feeling that standards were slipping. Consistency is tough at this volume. I’m sharing the solution we found, which has become our main product. Continue (https://docs.continue.dev) runs AI checks on every PR. Each check is a source-controlled markdown file in `.continue/checks/` that shows up as a GitHub status check. They run as full agents, not just reading the diff, but able to read/write files, run bash commands, and use a browser. If it finds…
Feb 2026 · docs.continue.dev
- 17WB
Hey HN, We’re two developers (co-founders) with a team of 20 who got tired of spending hours reviewing PRs, so we built Infinitcode.ai, an AI-powered code reviewer that: - *Summarizes PRs in plain English*: No more deciphering 1,000-line diff jungles - *Catches more than bugs*: Security holes, performance pitfalls, code smells, even typos (yes, we’ll flag “vurnerabilities” and vulnerabilities) - *Zero onboarding*: Works instantly—no “let me learn your codebase for weeks” nonsense. Why we’re posting: We’re in alpha and need brutal honesty. Roast our tool, mock our UI, or tell us why AI will…
2025 · infinitcode.ai
- 18
- 19WB
At Metabase, we built an AI agent called Repro-Bot that reads our GitHub issues and attempts to reproduce reported bugs automatically. It started as a hackathon project and is now part of our daily workflow, so we wrote about it and open-sourced the code as an example for others. How have similar tools been working for you? What has worked well and what has not?
Apr 2026 · metabase.com
- 20CA
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
- 21GA
Simon(sfarshid) and I spend a lot of time on GitHub. As data nerds we put together a quick tool to explore your repository’s data. How it works: - Data Loading: We use dlt to pull data (issues, PRs, commits, stars) from GitHub - Semantic Layer: Relta wraps the underlying dataset into a semantic layer so the LLM doesn’t hallucinate. - Text-to-SQL: A text-to-SQL agent transforms your plain-English question into a query using the semantic layer - Generative Charts: assistant-ui dynamically generates a chart based on the SQL query - Refinements: If the semantic layer can’t handle your question,…
2024 · github.com
- 22
- 23
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
- 24
Ranked by how close each launch is in meaning, then by votes. Refine with a description →