Why it matters
Screenshot & markup gives ForkMesh a concrete mechanism for visual captures annotated and attached to repo conversation. Capture any region of the screen, annotate it with built-in drawing tools, and drop it straight into an issue, PR, or chat.
A local-first forge needs the local app to be more than a mirror status screen. In ForkMesh, screenshot & markup 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 screenshot & markup 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: Capture any region of the screen, annotate it with built-in drawing tools, and drop it straight into an issue, PR, or chat. The same machine can hold the repository, review work, operate agents, and explain its own network state.
Where it fits
Use screenshot & markup 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 Screenshot & markup keeps visual captures annotated and attached to repo conversation connected to the repository, its signatures, and the nodes that serve it.