claude-code-merge-queue - Local merge queue for parallel Claude Code agents
Show HN: A local merge queue for parallel Claude Code agents
claude-code-merge-queue is a zero-cost, local tool that serializes parallel work from multiple Claude Code agents to prevent push races and redundant builds. Unlike GitHub's cloud-based Merge Queue, this solution runs entirely on your machine, eliminating action minute costs and working with any repository plan. It automatically manages numbered lanes, handles worktree creation, and enforces a FIFO landing process with customizable check commands. By integrating directly with Claude Code hooks and Git workflows, it ensures clean history and stable integration without requiring human reviews or external infrastructure.
Same idea — serialize landings, test before merge, keep history clean — run locally instead of in someone else's billed cloud.
- barrkel
A decent idea, however it seems to me a good chunk of it is because of git limitations. Have you looked jj?
I'm having a much better time with jj and a workspace per subagent than I was with git and worktrees.
It's still useful to have the CI gating on updating the master branch pointer, but you largely stop working with branches once you switch to jj.
- dpc_01234
SelfCI: https://radicle.network/nodes/radicle.dpc.pw/rad:z2tDzYbAXxT... , supports git & jj
- throwaw12
idea looks nice, but can you share what's your workflow to push 90 commits/day?
I understand each commit might have different size, but I am guessing your commits == Pull Request (because you need this constant merge queue to rebase, merge, test) and each are around 40-80 lines of code (additions and removals), and you are probably not reviewing the code because at this rate even if one commit takes 2 minutes to review we are talking about 3 hours of non stop code review.
if you are not reviewing each code, probably your commits are small items and 10-20 of them are a part of single PR, then how do you sustain working across multiple projects?