The queue command analyzes all completed worktrees and shows the optimal merge order based on commit count and file overlap. Optionally ships them all in sequence.

Usage

owt queue [OPTIONS]

Options

Option	Description
--base <branch>	Target base branch for merges
--ship	Ship all completed worktrees in optimal order
-y, --yes	Skip confirmation prompts

How It Works

owt queue inspects all worktrees with WAITING or COMPLETED status and ranks them by merge complexity using the MergeManager:

1. Commit count -- fewer commits merge first (less risk)
2. File overlap -- worktrees touching unique files merge before those with shared files

Worktrees with no file overlap and the fewest commits are placed at the front of the queue, so the lowest-risk merges land first.

Examples

View Merge Order

owt queue

Output:

         Merge Queue
┌───┬──────────────┬─────────┬─────────┐
│ # │ Worktree     │ Commits │ Overlap │
├───┼──────────────┼─────────┼─────────┤
│ 1 │ fix-typos    │ 2       │ 0 files │
│ 2 │ add-docs     │ 5       │ 0 files │
│ 3 │ auth-jwt     │ 12      │ 3 files │
└───┴──────────────┴─────────┴─────────┘

Ship All Completed Work

owt queue --ship

Ships each worktree in order: commit, merge, teardown, then move to the next.

Ship Without Confirmation

owt queue --ship --yes

When to Use

Scenario	Command
See what's ready to land	owt queue
Ship everything in one go	owt queue --ship
CI/CD automated merge	owt queue --ship --yes
Ship a single worktree	owt ship

See Also

• owt ship -- Ship a single worktree
• owt merge -- Two-phase merge with conflict guard
• The Control Plane -- Visual management