July 29, 2026
Merge queue? More like merge tea
Show HN: A local merge queue for parallel Claude Code agents
This DIY traffic cop for AI coding splits the crowd between “genius” and “why not just use CI?”
TLDR: A developer launched a free local tool to make multiple Claude coding agents take turns saving code safely instead of stepping on each other. Commenters were split between “smart and useful,” “my cloud setup already does this,” and the eternal tech flex: “have you tried a completely different tool instead?”
A new Show HN project is pitching itself as a free, local traffic controller for multiple Claude coding agents working at once. In plain English: if several AI helpers are all trying to save code, run heavy checks, and push changes at the same time, this tool makes them line up so they don’t crash into each other. It promises fewer messy race conditions, fewer duplicate builds, and less of that “who broke main?” chaos — all without paying for GitHub’s pricier cloud queue.
But the real action is in the comments, where the crowd instantly split into camps. One side basically said, cute idea, but my existing automated testing already does this. User orsorna gave the practical-eye-roll version: local tools are nice until your own machine becomes the bottleneck, while cloud systems are easier to scale. That sparked the classic builder-vs-infrastructure drama: do you trust your own laptop, or let the big platform babysit your code?
Then came the spicy software snobbery. barrkel swooped in with a hot take that this whole thing feels like a workaround for Git’s limitations, name-dropping an alternative tool, jj, like someone barging into a group chat to say everyone’s using the wrong app. Meanwhile, ElijahLynn brought the accidental comedy of the thread: instead of dismissing it, they basically said, same hat — revealing they’d spent two months building a very similar homemade system with elaborate tests and content stamps. So the mood was a delicious mix of admiration, skepticism, and that evergreen programmer punchline: everyone is independently inventing the same tool in their garage
Key Points
- •Claude Code Merge Queue is presented as a local merge queue that serializes parallel agent landings to prevent push races, redundant heavy builds, and flaky shared-resource tests.
- •The tool uses a single configuration file to define branches, lane naming, ports, regenerable files, build output handling, symlinks, and the command used to gate landings.
- •The article compares the tool with GitHub Merge Queue, stating that the local tool works on any plan and repository, costs $0 to run locally, and does not require a pull request.
- •Included commands cover worktree creation hooks, serialized builds, queued landing, checkout syncing, promotion to production, lane previewing, port lookup, and pruning landed worktrees.
- •A pre-push hook enforces the landing workflow by rejecting direct pushes to the integration branch and running the configured check command before permitting a landing.