Why it matters
Kanban board gives ForkMesh a concrete mechanism for visual issue planning inside the desktop repository workspace. Drag issues across columns to plan work visually, right inside the desktop app.
Planning loses force when it drifts away from the code history and pull requests it is supposed to guide. In ForkMesh, kanban board 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 kanban board through the same split it uses across the product: issues are repository-linked records surfaced in desktop and web views beside branches, pull requests, milestones, and agent sessions.
The behavior is intentionally narrow: Drag issues across columns to plan work visually, right inside the desktop app. State changes stay portable because the planning layer follows the repository instead of one private dashboard.
Where it fits
Use kanban board when triage and progress tracking should live beside the repository and remain portable.
It pairs with the rest of Issues & planning because Kanban board keeps visual issue planning inside the desktop repository workspace connected to the repository, its signatures, and the nodes that serve it.