Why it matters
Keyboard-first navigation gives ForkMesh a concrete mechanism for fast table and view navigation for long repo sessions. Shortcuts for every major view and arrow-key navigation across tables keep your hands on the keyboard.
A local-first forge needs the local app to be more than a mirror status screen. In ForkMesh, keyboard-first navigation 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 keyboard-first navigation 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: Shortcuts for every major view and arrow-key navigation across tables keep your hands on the keyboard. The same machine can hold the repository, review work, operate agents, and explain its own network state.
Where it fits
Use keyboard-first navigation 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 Keyboard-first navigation keeps fast table and view navigation for long repo sessions connected to the repository, its signatures, and the nodes that serve it.