Board Tab
Board is a kanban view of issues — manual or agent-created. Each card is an issue with a status, owner machine, and history; a detail page shows the full timeline plus links to the relevant chats and Activity events.
Board is the canonical view of what your agents are doing right now, distinct from the Activity tab’s record of what they just did.
What the Board is for
The Board is the canonical place to see every unit of work in flight across your workspace, whether you typed a chat prompt that escalated into a tracked task or whether the agent created the issue itself from a remote tool call. Frame the Board as “what your machines are doing right now” and the Activity tab as “what your machines just did” — both pull from the same daemon, but the Board is curated work and Activity is raw events. The implementation is in internal/desktop/services/board.
Columns and lifecycle
Issues live in columns that map to lifecycle states (Backlog, In Progress, Review, Done by default). An issue moves between columns three ways: drag-and-drop inside the kanban view, an explicit status change from the issue detail page, or a programmatic move from an agent that called the issue tool. Custom columns and column reordering are out of scope for this page.
Agents can create and update issues by calling the issue tools — see the issue CLI page for the full verb list.
Issue detail page
Clicking a card opens the detail view at #/board/{issueID}. The page shows the title, the description (rendered as Markdown), the current status, the attached machine, the owner, the chats this issue touches, and a timeline of state transitions. Edits sync back through service_crud.go so the change is visible in every other surface — CLI, web, fan-out — within the next heartbeat.
Creating issues from chat
There are two creation paths from the desktop. Manual creation is the New button on the Board, which opens a form. From a chat, the context menu offers “Track this in the Board”, which prefills the title and description from the surrounding turn. Both paths end up calling board.Create, which is the same entry point the cmdop issue create CLI verb uses.
Filtering and search
The lists panel exposes filters by status, owner machine, label, and recency. Filters compose as an intersection — picking “In Progress” and “owner = build-server” gives only cards that are both, never the union. The free-text search field is fuzzy and matches on title and description simultaneously.
Cross-references
Board is a Desktop-only surface; the CLI mirrors it via cmdop issue. The web cabinet does not render the kanban — it sits in observability mode and only shows the read-only timeline.