Why it matters
QR handoffs gives ForkMesh a concrete mechanism for scannable repo, invite, and address handoffs from desktop to phone. Repos, invites, and addresses render as QR codes for instant scannable handoff to a phone.
A local-first forge needs the local app to be more than a mirror status screen. In ForkMesh, QR handoffs 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 QR handoffs 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: Repos, invites, and addresses render as QR codes for instant scannable handoff to a phone. The same machine can hold the repository, review work, operate agents, and explain its own network state.
Where it fits
Use QR handoffs 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 QR handoffs keeps scannable repo, invite, and address handoffs from desktop to phone connected to the repository, its signatures, and the nodes that serve it.