Suggestions appear as you type. Use the up and down arrows to choose one and Enter to open it.

This page's audience our own tag's counts — open to see them
–Visits
–Page views
–Clicks to vendors
–Time on page
–Reading now
Clicks to vendors, by tool
  • –
Top countries
  • –
Devices
  • –

– · visits, page views and clicks counted by our own tag, which counts more than our checked analytics; every figure rounded down · how we count

Claude Code Merge Queue review

Free#23 of 26 in Merge Queue Software

A free, self-hosted FIFO queue for landing Claude Code worktree lanes on one machine.

6.0/10Editor score
Claude Code Merge Queue6.0 Visit funador

Reviewed by iTechGuides Editors · Editorial team · Updated Oct 2026

Claude Code Merge Queue coordinates parallel Claude Code agents working in Git worktrees. It is aimed at solo and small-scale users who want local lanes to land in order rather than collide on an integration branch. The tool is free, open source, self-hosted, and runs on Linux, macOS, and Windows. Installed as a development dependency with an npm-compatible package manager, it connects Claude Code’s WorktreeCreate hook with Git operations; it is not a hosted service for coordinating a team across machines.

Its workflow is the main reason to choose it. Landings are serialized FIFO: a lane is rebased and pushed to an integration branch, and a configured check command runs before landing. A machine-wide build lock also serializes builds. After a landing, the tool can synchronize the main checkout, preview a lane’s live working tree on that checkout, promote the integration branch to production, and prune sibling worktrees that have already landed. These commands make it a focused fit for developers managing parallel local agent work, rather than a general-purpose merge platform.

That local scope is also the key limitation. Claude Code Merge Queue is built around Claude Code and Git on one machine; its documented workflow does not cover GitHub, GitLab, or Bitbucket merge-queue operation, batch validation, or merge trains. Teams that need shared hosted queues or those validation patterns should choose a different tool. For an individual already organizing work in Claude Code worktrees, the free local queue can keep landings ordered and run a check before they reach the integration branch; users seeking broader repository-provider or team workflows should look elsewhere.

Claude Code Merge Queue pros and cons

  • Where it wins
    • Rebases and pushes lanes FIFO to an integration branch
    • Runs a configured check before landing
    • Syncs the main checkout and can promote changes to production
  • Where it doesn't
    • Limited to local, one-machine workflows
    • No documented GitHub, GitLab, or Bitbucket merge-queue support
    • No batch validation or merge trains

Claude Code Merge Queue fact sheet, pricing and score →

Advertiser disclosure: iTechGuides is reader-supported. Vendors can pay for top positions in our rankings and for a place on other products' pages, and we may earn a commission when you click some links. Bought places stand at the number bought; this page and our disclosure say so. Paying vendors may get a fuller, more detailed review from our editors, and that review can change their score. How we rank.

Last updated · How we research and update