Operator Desk

The Operator Desk is the signed-in Meshive web app. It keeps the shell mounted while you move between workspace roll-ups, project views, task graphs, and step details.

Navigation model

The sidebar has workspace-wide views at the top and project-scoped views under each project.

• Dashboard shows total tasks, pending gates, running agents, completed work, active tasks, recent artifacts, and recent activity. It can export the current activity scope as CSV.
• Inbox lists steps waiting for a human decision. You can approve or reject inline, or open the task graph for context.
• Activity is the newest-first audit trail for task creation, step starts and completions, artifacts, gate requests and decisions, and board moves.
• Agent tokens is the account-level connection registry for MCP agents.

Each project has:

• Dashboard for project-only health and recent work.
• Tasks for the draggable board.
• Issues for the human backlog and task links.
• Inbox for project-only gates.
• Activity for project-only audit history.

Tasks and graphs

The Tasks view is a board with candidate, queued, running, awaiting_decision, done, wont_do, and failed columns. Operators can drag cards between columns. Agents should also report board changes with set_task_state so the board reflects their current view of the work.

Opening a task shows its step graph. The graph is laid out from the task DAG and is read-only: selecting a step opens the right detail pane. Gate steps open on the gate tab by default.

The detail pane shows:

• task context, board state, branch, and linked issues;
• step status, run metadata, dependencies, and description;
• the agent brief with objective, instructions, context artifacts, references, bounds, and acceptance criteria;
• artifacts attached to the step;
• gate approval controls when the step is a human gate.

Issues

Issues are project-scoped work items with keys such as WEB#12. Operators can create issues, change priority, change manual status when the issue has no linked tasks, and link or unlink resolving tasks.

When an issue has linked tasks, its status is derived from those tasks’ board columns. Moving a task can therefore move its linked issues.

Agent tokens

Agent tokens are created in the Agent tokens page. The current create flow selects a workspace and token name, then shows the raw bearer token once. Meshive stores only the token hash and short prefix afterward.

The token row shows connection status, workspace, project scope count, last seen time, and creation time. Revoking a token prevents future MCP handshakes and tool calls.

Public and protected routes

The Operator Desk requires Clerk sign-in. MCP uses bearer-token authentication at /api/mcp.