Skip to content

Dashboard Features

The Mentu dashboard provides a comprehensive set of views and tools for managing your commitment pipeline. This page covers each feature in detail.

The landing page after login. Provides a high-level overview of your workspace health:

  • Commitment counts by state: open, claimed, in_review, closed, dismissed
  • Recent activity feed showing the latest operations
  • Quick stats — commitments opened today, average time-to-close, active agents

This view gives you an at-a-glance understanding of pipeline throughput and where attention is needed.

The primary working view. Displays all commitments in the workspace as a filterable, sortable list.

  • Filter by state: open, claimed, in_review, closed, dismissed
  • Filter by actor: see only commitments claimed by a specific agent or human
  • Filter by tags: narrow down by classification labels
  • Full-text search across commitment titles and descriptions

Each commitment displays a color-coded badge indicating its current state:

StateBadgeMeaning
openBlueAwaiting someone to claim it
claimedYellowAn actor is actively working on it
in_reviewPurpleSubmitted, awaiting approval
closedGreenCompleted with evidence
dismissedGrayDiscarded without completion

Click any commitment to open its detail page, which shows:

  • The full state timeline — every operation that touched this commitment, rendered as a vertical timeline with timestamps and actors
  • Evidence chain — all evidence items submitted with the commitment (PR links, build logs, test results)
  • Related memories — any memories referenced by the commitment
  • Action buttons — contextual actions based on current state

From the detail page (or inline in the list), you can perform state-changing actions. Each action fires a POST /ops request to the Mentu API.

ActionOperationFrom StateTo State
Approveclosein_reviewclosed
Submitsubmitclaimedin_review
Reopenreopenclosed / dismissedopen
Dismissdismissopen / claimeddismissed

Actions are only available when they are valid for the commitment’s current state. Invalid transitions are disabled in the UI.

Browse and manage all memories captured in the workspace. Memories are context objects — bug reports, decisions, annotations, notes — that inform commitment work.

Each memory displays a badge for its kind:

KindDescription
bugBug report captured by the BugReporter SDK or manually
contextBackground context for a task or project
decisionAn architectural or process decision
noteGeneral-purpose annotation

Click any memory to view its full content. From the detail view, you can add annotations — follow-up notes that append to the memory without modifying the original capture.

The raw, chronological operation log. Every operation that has been applied to the workspace appears here in time-descending order.

The ledger is fully searchable. Search by:

  • Operation type (commit, claim, submit, close, capture, etc.)
  • Actor (human:rashid, agent:claude, etc.)
  • Payload content (free-text search into operation payloads)

This view is invaluable for debugging and auditing — you can reconstruct the exact sequence of events that led to any state.

The Bridge is the command queue for remote agent execution. It enables asynchronous communication between the dashboard and agents running in development environments.

Queue commands from the dashboard that agents will pick up and execute:

  • View pending commands waiting for agent pickup
  • See completed commands with their results
  • Cancel commands that are no longer needed

The Bridge displays connected machines and their health:

  • Online — agent is connected and polling for commands
  • Offline — agent has not checked in recently
  • Busy — agent is currently executing a command

An alternative view for commitment management. Commitments are organized into columns by state:

| Open | Claimed | In Review | Closed |
|------|---------|-----------|--------|
| ... | ... | ... | ... |

Drag and drop commitments between columns to trigger state transitions. The board enforces valid transitions — you cannot drag a commitment to an invalid state.

Workspace configuration and integrations.

Map external identities to Mentu actors. For example, map a GitHub username to a human: actor so that PR events are correctly attributed.

Connect your GitHub repositories to the workspace:

  • Automatic commitment creation from GitHub Issues
  • PR status synced to commitment evidence
  • Label management (mentu-tracked, claude, autonomous)

Set up outgoing webhooks to notify external systems when operations occur:

  • Configure webhook URLs
  • Select which operation types trigger the webhook
  • View delivery logs and retry failed deliveries

The dashboard uses Supabase Realtime subscriptions to receive live updates. When any operation arrives in the operations table:

  1. The subscription fires immediately
  2. The relevant view updates without a page refresh
  3. State badges, counts, and timelines all reflect the new state

This means multiple team members can watch the same workspace and see changes as they happen — when an agent submits a commitment, the team lead sees it move to in_review instantly.