Worktree board and agent states

The Worktrees tab shows every worktree of the current repository as a card, sorted into columns by what it is doing. When coding agents work in worktrees, this is where you see which ones are still setting up, which have changes, which are ready to push and which can go.

Where to find it

• Worktrees tab at the top of the window, or ⌘3.
• View › Worktrees, or Command palette › Show worktrees.
• Sidebar footer: "N worktrees" with Show all.

The header

The heading reads "Worktrees", then a line such as "4 worktrees of api, 2 with changes". To its right:

Columns

The default branch is origin/HEAD, or main, master or trunk if the remote has no HEAD. A worktree counts as merged when its branch is in git branch --merged against the default branch and isn't sitting at the default branch's tip (unless the remote branch is gone).

States

Each card carries a pill with one of these states, in this order of priority.

Under the pill a card shows the repository name (or "api, main folder" for the main checkout), the branch, and a note that depends on the state:

• Removing: "Removing the folder. The branch stays."
• Folder missing: "The folder was deleted. Clean up to forget it."
• Merged or gone: "Safe to remove, 412 MB". Disk use is measured with du two worktrees at a time, only for cards that are on screen.
• The worktree open in this window: "Open in this window".
• Marked by an agent, with a note: the note and how long ago it was set. See Coding agents.
• Otherwise the last commit's summary, or "No commits yet".

Then the stats line: "N files changed" or "No changes", the ahead and behind counts, and "no upstream" when there isn't one.

Actions on a card

Double-clicking a row in the List layout opens that worktree.

Removing a worktree

Every removal asks first, and the question depends on what would be lost:

• Clean and pushed: "Remove the name worktree?" Deletes the folder; the branch and its commits stay. Answer: Remove worktree.
• Uncommitted changes: "name has uncommitted changes". Answers: Cancel, Remove and lose changes, or Commit first, which opens the worktree on its Changes tab.
• Commits not on the remote: "name isn't on the remote". Answers: Cancel, Remove without pushing, or Push, then remove.

Removing several at once combines these: the dialog lists the worktrees with uncommitted changes and those not on the remote (the first four by name, then "and N more"), and offers Remove all and lose changes, Push, then remove, or Remove the safe ones.

Selecting several

Tick a card's checkbox, ⌘-click a card to add it, or ⇧-click to pick a run of cards. A bar then shows "N selected" with Select all N or Select none, Add merged or gone, Clear, and Remove N. esc clears the selection. The hint under the board reads "⌘-click or tick worktrees to remove several at once. ⇧-click picks a run."

The List layout

Columns: Worktree, Status, Changes, Ahead, behind, Last commit. Sort order follows the board's grouping.

When there are no worktrees

The board shows "Only the main folder so far." with a line explaining that a worktree checks out another branch in its own folder, so you (or an agent) can work on it without stashing or switching here, and a New worktree button.

Free and Pro

From Mergepond 1.0.7 the board is part of Pro. Worktrees themselves are free: you can create, open and remove them on Free.

On Free, the Worktrees tab lists every worktree with its branch and folder, an Open button (Show changes for the worktree open in this window) and a ⋯ menu. Under the list, "See every worktree's status with Pro" explains what the board adds, with Buy Pro and Enter licence key.

Pro adds:

• the Board, Grid and List layouts;
• the state pills and the columns they sort into;
• the marks that show which worktrees a coding agent is working in, has ready for review or has finished;
• selecting several worktrees to remove at once;
• Clean up.

On Free:

Related guides

• Let your coding agent make its own worktrees
• Coding agents in worktrees
• Git worktrees tutorial