Hand off the issue.
Review the PR.

MergeMill runs several coding agents in parallel, each in its own git worktree, and takes every feature from plan to merged pull request. You approve what runs, cap what it spends and decide what merges.

Uses your existing Claude Code login · Apple Silicon and Windows x64

MERGEMILL5H 31%

FEATURE · ENG-412

Move session tokens to httpOnly cookies

  1. ✓ Plan
  2. ✓ Spec
  3. ● Build
  4. Review
  5. PR
  6. Merge
  • Vega · slice 1/3

    Waiting for approval: npm test

    $0.42
  • Orion · slice 2/3

    Editing src/session/cookies.ts

    $0.31
  • Lyra · slice 3/3

    Blocked by slice 1, starts when it merges

    $0.00

APPROVAL · VEGA wants to run

$ npm test -- session

A Allow onceS For sessionD Deny

Why MergeMill

One agent at a time is slow. Five in one checkout is chaos.

Coding agents are good enough to do real work, but running them well means juggling terminals, branches, approvals and bills. MergeMill does the juggling, so your attention goes on the decisions.

How it works

From issue to merged PR, with you at the checkpoints.

Start a feature from a sentence or a Linear issue. A different agent takes each step, and you approve the moments that matter.

  1. Plan

    An agent interviews you about the feature until the plan is right, then writes it down.

    You: approve the plan or ask for changes

  2. Spec

    The plan becomes a spec, carved into small slices that can each ship alone, with what blocks what.

    You: approve the spec and slices together

  3. Build

    Every unblocked slice gets its own agent and worktree, is built test-first, and is merged into the feature branch.

    You: answer approvals and questions

  4. Review

    A fresh agent reviews the whole branch, fixes problems and flags what a human must look at.

    You: read the flagged areas

  5. PR

    The pull request is opened with a proper description and the flagged areas as inline comments.

    You: review it like any PR

  6. Merge

    An agent watches CI and review comments and fixes what comes up, until the PR is green.

    You: squash-merge when ready

Every step's prompt, skills, model and pre-approved tools are yours to change. Add steps such as Test, which starts the dev servers for you to try the feature, or Publish, which posts the plan and spec to Linear, or write your own.

Features

Everything you'd otherwise build yourself.

Anywhere

Close the laptop. The work keeps going.

One engine, four ways to reach it. Approve a command from your phone, check in over SSH, or hand a feature to a server at home.

Compared

Versus a few terminal tabs.

Agents in terminal tabsMergeMill
Running several at onceAgents share a checkout and trip over each otherA worktree and branch per agent, merged back cleanly
Knowing what needs youFlip through tabs to find the one that's waitingApprovals and questions in one place, with notifications
CostFind out when the bill arrivesLive per task, with caps per task and per feature
Getting to a PRYou plan, review, open and babysit itPlan, spec, build, review, PR and merge as steps
Your issue trackerCopy and paste the issue, update it by handLinear issues in, statuses and documents updated for you
When you walk awayWork stops when the laptop sleepsApprove from your phone, or hand off to a server

Start your first feature in five minutes.

MergeMill was built for personal use with a Claude subscription. If you build on it for other people, use API key authentication instead.

  1. Install and open MergeMill

    Signed and notarized on macOS. It keeps itself up to date from then on.

  2. Be signed in to Claude Code

    MergeMill uses that login. Add the GitHub CLI for pull requests and a Linear key if you use Linear.

  3. Pick a repo and start a feature

    Describe it in a sentence or choose a Linear issue. Approve the plan, and the work begins.