Dynamic Dashboards
Agent-defined dashboards via dashboard.yaml with 11 widget types, historical tracking, and sparkline charts.
Why Every AI Agent Needs a GitHub Repo — dashboards
Apr 2026
Build and Deploy Agents in Cursor
Apr 2026

Concepts
metric, status, progress, table, list, chart, text, badge, countdown, link, image.agent_dashboard_values table over time, enabling trend analysis.dashboard.yaml) showing Tasks 24h, Success Rate, Cost, and Health.How It Works
The agent writes a dashboard.yaml file to its workspace.
The file defines widgets with type, title, value, and optional configuration fields.
Open the agent detail page and select the Dashboard tab to see the widgets.
Auto-refresh updates values as the agent modifies the YAML file.
Historical values are tracked automatically — sparklines appear for metrics with enough data points.
Trend indicators (↑/↓) show percentage change from previous values.
A Platform Metrics section appears at the bottom of every dashboard, showing Tasks 24h, Success Rate, Cost, and Health. This section is auto-injected and not controlled by the YAML file.
Related: the Brain Orb
The dashboard.yaml widgets above are one way an agent renders its own state. Knowledge-base agents — like the bundled Cornelius second-brain — can also publish a Brain Orb: a self-rendering "mind" page that draws the agent's own notes, edges, and activity as a live 3D knowledge graph on the agent's Brain tab.

The Brain Orb is a capability-gated surface: it appears only for agents that ship the brain-orb capability (Cornelius-class agents) and only when the platform Brain Orb flag is enabled — it is off by default. The agent owns generation and scope state; Trinity reads and renders it.
For Agents
Agents control their dashboard entirely by writing to dashboard.yamlin their workspace. No API call is needed to publish changes — the file is read on each dashboard request.
API
| Endpoint | Method | Description |
|---|---|---|
| /api/agents/{name}/dashboard | GET | Get dashboard data |
Query Parameters
| Parameter | Type | Description |
|---|---|---|
| include_history | bool | Include historical value data |
| history_hours | int | Number of hours of history to return |
| include_platform_metrics | bool | Include the auto-injected platform metrics section |