Alternatives
Products that do what Multi-Agent-Coder Is #12 on Stanford's TBench. Beats Claude Code does
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…
- 1
- 22C
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
- 3TB
After training calculator agent via RL, I really wanted to go bigger! So I built RL infrastructure for training long-horizon terminal/coding agents that scales from 2x A100s to 32x H100s (~$1M worth of compute!) Without any training, my 32B agent hit #19 on Terminal-Bench leaderboard, beating Stanford's Terminus-Qwen3-235B-A22! With training... well, too expensive, but I bet the results would be good! *What I did*: - Created a Claude Code-inspired agent (system msg + tools) - Built Docker-isolated GRPO training where each rollout gets its own container - Developed a multi-agent…
2025 · github.com
- 4
AgentGrid▲77Hi HN, I’m Michael, I built AgentGrid with my friend Souren because we were tired of losing our coding sessions and couldn't keep track of what was actually being built across our many projects. Our approach was to use an infinite canvas desktop app for the TUIs we already know and love, mainly claude + codex. We drew inspiration from Figma and Railway. Overtime we added image nodes, notes, terminals, coding editors, source control, etc. I wasn't sure about it at first. It took me a month to give the first version Souren built a real try. What got me was an Apple System Update I've been…
Jul 2026 · agentgrid.sh
- 5
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
- 6IB
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
- 7
Hi y'all. Been working on something that should've been made a long time ago imo. It compiles codebases into O(1) hashmaps that the agent queries to discover the structure of your code/answer questions/write code. It also does complete static analysis checks on any writes the agent makes. Don't take my word for it though. Here are the benchmarks: https://benzi.fly.dev/benchmark. on 2/20 tests, Claude Code (mostly Sonnet on one task) regressed or timed out. Benzi didn't because of course, it has a map it can query and not get lost in the sauce. On the other 18 it…
29d ago · benzi.fly.dev
- 8
Hola HN! Long time lurker, sometimes commentor, first time poster here. I’ve been working alongside my two co-founders and a few colleagues on a project I’m excited (and a little nervous) to share with you all! Like many of us, I’ve lived a tortured existence with AI coding (is it vibes?) over the past few months - I think November was a big moment with this. But, one thing I’ve noticed after building orchestration layer after orchestration layer is that the thing I always came back to was “what the hell is Claude Code actually doing?” Perhaps it’s because of the time Claude Code got…
Jun 2026 · backplanes.com
- 9AR
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
- 10IB
Hey HN. I built an AI agent harness over the past few months and I'm open sourcing it today. Some context on why. I've been building with Claude Code daily using this harness. It orchestrates multiple AI agents as a team, with a dashboard, chat, kanban board, the works. I used it to build a full SaaS product (MyUpMonitor, https://myupmonitor.com) in about 24 hours of focused coding. Then yesterday Anthropic announced Mythos and decided to keep it behind closed doors. Meanwhile I'm paying for Claude and I can't access their best model. I don't think that is nice at all... So I'm…
Apr 2026 · 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
- 12LL
Some time ago I built a simple app to run swarms of coding agents — I call it fleet (https://news.ycombinator.com/item?id=48256389). It's based on centralized beads with a Python orchestrator and can run any coder (Claude, agy, Codex). Recently I added a UI to manage the whole agent lifecycle: adding new tasks, monitoring running ones, and a chat interface built on MCP with a centralized SQLite DB. From the UI I can spawn agents to run in any directory, define dependencies on other tasks, and specify which coder/model should do the job. Today I can run 10–15 agents…
Jun 2026
- 13OA
Hi HN, I’m Mike, the founder of OpenRig. I built this because my Claude Code + Codex setup kept forming little "topologies" of long-lived agents that worked well together, but the terminal sprawl was intense. So I built a primitive the agents could intuitively reach for to save and recreate these setups on the fly. This then led to more agent-first primitives like coordination, declarative workflow patterns, workspaces, etc. Several months in and these "rigs" I manage with openrig require a lot less babysitting and I can manage more projects at once without getting overwhelmed. The short…
May 2026 · openrig.dev
- 141D
We just open-sourced the internal system we built at Assembled for running coding agents as a team. Coding agents worked well for individual engineers, but the surrounding workflow was a bit of a mess. We generally found that many engineers had different MCP connections and context for their agents, personal automations running that other people couldn’t access, and very little introspection for what a human’s input into the coding agent looked like. So we built an internal system that converted coding agents into shared team infrastructure. The system runs Codex, Claude Code, OpenCode, and…
Jun 2026
- 15AP
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
- 16WB
Hi HN — we built agentcall.dev because the coding agent you're already running in your terminal shouldn't be trapped there. The pitch: your existing Claude Code, Codex, OpenClaw, or Cursor session joins a Google Meet, Teams, or Zoom call as itself. Same session, same context, same file access. It speaks, listens, screen-shares a localhost webpage, and can code live while you all talk about what it's building. What's actually on the call: • Voice in, voice out. Two modes — collaborative (sub-second via a voice intelligence layer tuned for latency) or direct (~2s, your coding agent itself…
Apr 2026
- 17
- 18CR
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
- 19OV
Jun 2026 · github.com
- 20YA
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
- 21BC
We are a small group of undergrads interested in building human in the loop coding agents. We dream of a world where building complex agent workflows feels as simple and creative as playing with legos. When we were building stuff we needed a tool that made it easy to try out different code embedding models so that we could see which ones worked best in different scenarios and understand their strengths and weaknesses. So to speed that process up we made PurpleSearch an 'instant' search engine for your local codebases. This tool lets you quickly deploy any open source embedding model on…
2025
- 22FA
Founder here. I built NEO, an AI agent designed specifically for AI and ML engineering workflows, after repeatedly hitting the same wall with existing tools: they work for short, linear tasks, but fall apart once workflows become long-running, stateful, and feedback-driven. In real ML work, you don’t just generate code and move on. You explore data, train models, evaluate results, adjust assumptions, rerun experiments, compare metrics, generate artifacts, and iterate; often over hours or days. Most modern coding agents already go beyond single prompts. They can plan steps, write files, run…
Jan 2026 · marketplace.visualstudio.com
- 23IV
Coding agent management is all the rage right now, and many tools are being created to fill the gap. As a power user for all tools I've used since I've started my software engineering career, I've always taken the time to test multiple tools thoroughly before deciding on one, and an agentic manager was no different. I've tested many tools, but ultimately landed on Agent of Empires (AoE for short). Why ? Because it's fast, the development is active and it's feature complete, and easy to contribute to. So I did (contribute). In my day to day workflow for my job, I need the ability to start…
May 2026 · github.com
- 24
Ranked by how close each launch is in meaning, then by votes. Refine with a description →