Guides

Each guide walks you through one job, start to finish, in the real app. If you want the full reference for a view or a sheet, that lives in the docs.

Get started

Install Mergepond and open your first repo
Download, open a repository, and find your way around the three views.
Switching from Fork
Where Fork habits land in Mergepond, and what Mergepond does differently.
Everything from the keyboard with ⌘K
Run commands, switch branches and jump to commits without reaching for the mouse.

Git worktrees tutorial: several branches at once
What a worktree is, the plain Git commands, and the same thing done in Mergepond.
Worktrees that set themselves up
A folder pattern and a setup recipe, so every new worktree is ready to run.
Run coding agents in parallel with Git worktrees
Give each agent its own worktree, watch them on the board, review and clean up.
Let your coding agent make its own worktrees
Install the Mergepond plugin in Claude Code or wire up Codex, and the agent makes, sets up and marks its own worktrees.

Use a Git GUI on repos over SSH
Open a repository on a dev box or server and work on it as if it were local.

Workspaces, windows and Git identities
One window per client or project, each with its own colour and commit identity.

Stage and commit precisely
Stage whole files or single hunks, write the message, amend when you need to.
Rebase by dragging
Reorder, squash, reword and drop commits in a sheet, then start the rebase.
Resolve merge conflicts
Pick a side per conflict, keep both, or edit by hand, then continue the merge.
Find any commit: search, history and blame
Filter the history by message, author, path and date, then follow a file back.
Pull requests from your Git host
Check out a pull request into its own worktree, review it, push your reply.

Colour schemes, shortcuts and settings
Pick a scheme, follow macOS light and dark, learn the shortcuts, enter a licence.

Missing a guide? Write to hello@mergepond.dev and say what you were trying to do.