Why it matters
Complete repository workspace gives ForkMesh a concrete mechanism for one desktop workspace for code, reviews, agents, planning, releases, and node operations. Code, Commits, Issues, Agents, Pull requests, Discussions, Actions, Security, Quality, Insights, Branches, Worktrees, Releases, Mirror nodes, Artifacts, Shortcuts, and Settings, every view one click apart.
A local-first forge needs the local app to be more than a mirror status screen. In ForkMesh, complete repository workspace 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 complete repository workspace 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: Code, Commits, Issues, Agents, Pull requests, Discussions, Actions, Security, Quality, Insights, Branches, Worktrees, Releases, Mirror nodes, Artifacts, Shortcuts, and Settings, every view one click apart. The same machine can hold the repository, review work, operate agents, and explain its own network state.
Where it fits
Use complete repository workspace 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 Complete repository workspace keeps one desktop workspace for code, reviews, agents, planning, releases, and node operations connected to the repository, its signatures, and the nodes that serve it.