Blog
Notes from making Mergepond: how Git worktrees change the way you work, what running coding agents in parallel really needs, and the decisions behind the app. Subscribe with RSS.
Why we built Mergepond
Good Git clients exist. None of them treated worktrees, remote machines or several identities as the normal case, so we wrote one that does.
How to run several coding agents on one repo without collisions
A folder and a branch per agent, a board to watch them, and a review step before anything merges. The practice, with the Git underneath it.
Git worktrees vs stash vs a second clone: when each one wins
Three ways to work on two things at once, what each costs, and the one rule for choosing between them.