Many agents at once
Give each agent its own branch and land all of them with one merge and one test run.
Why one call
A merge queue lands pull requests one at a time and reruns the tests after every rebase, so eight agents finishing together wait in line. land merges all of their branches at once, tests the combination once, and lands every branch that keeps the tests green.
Set it up
Give each agent its own worktree and branch so they never share uncommitted files. When they finish, one agent runs land merge with every finished branch. The order only breaks ties.
# each agent works in its own worktree and branch git worktree add ../api -b agent/api git worktree add ../ledger -b agent/ledger git worktree add ../email -b agent/email # when they finish, one agent merges every branch in one call git fetch origin main land merge agent/api agent/ledger agent/email --onto main --json
land refuses a branch whose worktree has uncommitted or untracked files, so stale work never lands as green. The verdict says which worktree and the command to fix it.
When one branch breaks
The others still land. The refused branch comes back with the failing test, its assertion, the branch it clashes with (hitBy) and a command that reproduces the failure on the exact merged code. The agent fixes its branch on top of what landed and merges again. See Reading a verdict.
Subagents
A subagent is just another branch. The agent that started it commits the subagent's worktree and includes its branch in the same land merge call.