Why it matters
Source control & worktrees gives ForkMesh a concrete mechanism for Git staging, branching, commits, and worktrees controlled from the desktop app. Stage, commit, branch, and manage multiple worktrees from the app, including the worktrees your agents are working in.
A local-first forge needs the local app to be more than a mirror status screen. In ForkMesh, source control & worktrees addresses that need at the feature level, keeping the behavior close to the repository instead of buried in a detached hosted layer.
How ForkMesh handles it
ForkMesh handles source control & worktrees through the same split it uses across the product: the Qt desktop node combines repo browsing, source control, worktrees, markdown, captures, shortcuts, diagnostics, and handoff flows around the hosted mirror.
The behavior is intentionally narrow: Stage, commit, branch, and manage multiple worktrees from the app, including the worktrees your agents are working in. The same machine can hold the repository, review work, operate agents, and explain its own network state.
Where it fits
Use source control & worktrees when the machine hosting the code should also be the place where contributors understand and act on it.
It pairs with the rest of The desktop app because Source control & worktrees keeps Git staging, branching, commits, and worktrees controlled from the desktop app connected to the repository, its signatures, and the nodes that serve it.