Why it matters
Fork with intent gives ForkMesh a concrete mechanism for choosing the exact local destination when forking a mesh repository. Fork any repository in the mesh and choose exactly where the copy lands in your working tree.
A local-first forge needs the local app to be more than a mirror status screen. In ForkMesh, fork with intent 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 fork with intent 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: Fork any repository in the mesh and choose exactly where the copy lands in your working tree. The same machine can hold the repository, review work, operate agents, and explain its own network state.
Where it fits
Use fork with intent 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 Fork with intent keeps choosing the exact local destination when forking a mesh repository connected to the repository, its signatures, and the nodes that serve it.