Hey HN, I'm Prateek. About a week ago I started building a tool to manage my AI coding agents. In 8 days and 134 commits it's merged 80+ of its own PRs and largely built itself. 2,700+ GitHub stars in two weeks.
It started super hacky. I was running a bunch of Claude Code sessions and just built a quick agent that could switch between them and take me to the right session at the right time. That alone got me to 13 PRs in a day.
Then I started using that same agent to plan too — look at what's in the backlog, figure out what matters most, scope tasks, send agents off. So I took the hacky version and pointed it at building the proper version. It's been building itself since.
Each agent gets its own git worktree and branch. There's a dashboard so I can see what's going on — which agents are working, what PRs are open, what's failing CI, what has review comments. A merge queue handles rebasing when things land so downstream agents don't build against stale main. If CI breaks, the agent gets the logs and retries. If someone leaves a review comment, the agent addresses it.
The orchestrator itself is an agent too — it reads the backlog, decides what to prioritize, breaks it down, spawns agents. I mostly just review PRs at this point. At peak I had ~16 going in parallel on the same repo.
Works with Claude Code, Codex, Aider. Tmux or Docker. GitHub or Linear. Everything's pluggable.
Hey HN, I'm Prateek. About a week ago I started building a tool to manage my AI coding agents. In 8 days and 134 commits it's merged 80+ of its own PRs and largely built itself. 2,700+ GitHub stars in two weeks.
It started super hacky. I was running a bunch of Claude Code sessions and just built a quick agent that could switch between them and take me to the right session at the right time. That alone got me to 13 PRs in a day.
Then I started using that same agent to plan too — look at what's in the backlog, figure out what matters most, scope tasks, send agents off. So I took the hacky version and pointed it at building the proper version. It's been building itself since.
Each agent gets its own git worktree and branch. There's a dashboard so I can see what's going on — which agents are working, what PRs are open, what's failing CI, what has review comments. A merge queue handles rebasing when things land so downstream agents don't build against stale main. If CI breaks, the agent gets the logs and retries. If someone leaves a review comment, the agent addresses it.
The orchestrator itself is an agent too — it reads the backlog, decides what to prioritize, breaks it down, spawns agents. I mostly just review PRs at this point. At peak I had ~16 going in parallel on the same repo.
Works with Claude Code, Codex, Aider. Tmux or Docker. GitHub or Linear. Everything's pluggable.
Wrote up how the whole thing works here: https://x.com/agent_wrapper/status/2025986105485733945
Curious if anyone else is running multiple coding agents and what you've tried for coordination.