II.
Page JSON
Structured · livepage:docs-user-guide-ecosystem-observer-dashboard
observer-dashboard — real-time run observability json
Inspect the normalized record payload exactly as the atlas UI reads it.
{
"id": "page:docs-user-guide-ecosystem-observer-dashboard",
"_kind": "Page",
"_file": "wiki/docs/user-guide/ecosystem/observer-dashboard.md",
"_cluster": "wiki",
"attributes": {
"nodeKind": "Page",
"sourcePath": "docs/user-guide/ecosystem/observer-dashboard.md",
"sourceKind": "repo-docs",
"title": "observer-dashboard — real-time run observability",
"displayName": "observer-dashboard — real-time run observability",
"slug": "docs/user-guide/ecosystem/observer-dashboard",
"articlePath": "wiki/docs/user-guide/ecosystem/observer-dashboard.md",
"article": "\n[Docs](../index.md) › [Ecosystem](./overview.md) › observer-dashboard\n\n# observer-dashboard — real-time run observability\n\n**Package:** `@a5c-ai/babysitter-observer-dashboard` · **Version:** 6.0.0 · **Maturity:** GA\n\n**The observer dashboard is a real-time observability UI for Babysitter orchestration runs. It streams run events over SSE and renders task progress, journal events, and orchestration state live in your browser.**\n\nBecause every run is event-sourced, the dashboard does not need to poll or guess — it simply consumes the same immutable journal the engine writes, as it is written.\n\n---\n\n## On this page\n\n- [What it is](#what-it-is)\n- [How to launch it](#how-to-launch-it)\n- [How it works](#how-it-works)\n- [Who uses it](#who-uses-it)\n- [Next steps](#next-steps)\n\n---\n\n## What it is\n\nPer its package description, it is the \"real-time observability dashboard for babysitter orchestration runs.\" It is built on **Next.js** (the v6 announcement cites Next.js 16 / React 19), streams run events via **Server-Sent Events (SSE)**, virtualizes large run histories with `@tanstack/react-virtual`, and uses the Compendium design system. It renders task progress, journal events, and orchestration state in the browser.\n\n---\n\n## How to launch it\n\nThe dashboard ships a bin and is also launchable from inside a harness:\n\n```bash\n# In-session (Claude Code and other harnesses):\n/babysitter:observe\n\n# Via the genty runtime CLI:\ngenty observe\n```\n\nThe underlying bin is `babysitter-observer-dashboard` (`dist/cli.js`). Source lives under `packages/observer-dashboard/src/` (`app/`, `components/`, `lib/`, `cli.ts`).\n\n---\n\n## How it works\n\n```\nEngine appends events → immutable journal (~/.a5c/runs/<runId>/) → SSE stream → Dashboard\n```\n\nThe engine writes journal events as the run progresses; the dashboard subscribes to the stream and renders them. Large histories are virtualized so the UI stays responsive on long-running or high-volume runs.\n\n---\n\n## Who uses it\n\nAnyone monitoring a live or historical Babysitter run — to watch convergence, see which task is executing, inspect the journal, or debug why a run stopped at a gate.\n\n---\n\n## Next steps\n\n- **See where it sits:** [Architecture & How It Fits Together](../architecture.md)\n- **What it streams:** [Journal System](../features/journal-system.md)\n- **Launch it from a harness:** [Slash Commands](../reference/slash-commands.md) (`/babysitter:observe`)\n- **Ecosystem map:** [Ecosystem Overview](./overview.md)\n",
"documents": []
},
"outgoingEdges": [],
"incomingEdges": [
{
"from": "page:docs-user-guide",
"to": "page:docs-user-guide-ecosystem-observer-dashboard",
"kind": "contains_page"
}
]
}