Skip to main content
subagent CX Codex

dashboard-operator — Claude Code subagent: what it does and setup

dashboard-operator monitors the Claude Code Agent Monitor dashboard on port 4820, tracks active agent sessions, and guides service restarts.

MIT ★ 1,198 updated 2026-10-23

Install into Claude Code · Plugin marketplace All methods and platforms ↓
/plugin marketplace add hoangsonww/Claude-Code-Agent-Monitor
/plugin install ccam-dashboard@claude-code-agent-monitor-plugins
Open on GitHub

What dashboard-operator does

The subagent oversees the Claude Code Agent Monitor instance at http://localhost:4820. It queries endpoints with curl or interacts via the bundled ccam-dashboard MCP server to inspect system state. The agent gathers runtime telemetry from /api/stats, including session counts, agent statuses, event totals, and WebSocket connections, while pulling database size and version metadata from /api/settings/info.

Built on the sonnet model, it relies on Bash, Read, and Grep tools. When the server goes offline, the agent marks it DOWN and provides exact startup instructions: npm run setup followed by npm start for production, or npm run dev for local development. Repository updates rely on npm run update:pull-setup.

All operations remain strictly read-only: the subagent never modifies data or triggers bulk imports on its own, instead directing the user toward /api/import/* routes when loading transcripts.

What it helps with

  • inspect Claude Code Agent Monitor health on port 4820
  • retrieve live agent counts and session stats from /api/stats
  • verify version status and updates via /api/updates/status
  • view instructions for transcript imports using /api/import/guide

Example prompts for the agent

  • Check if the dashboard on port 4820 is online and report stats
  • The monitor is unreachable, show the commands to start it
  • Inspect /api/settings/info and tell me the database size

How to install dashboard-operator

1Plugin marketplace

/plugin marketplace add hoangsonww/Claude-Code-Agent-Monitor
/plugin install ccam-dashboard@claude-code-agent-monitor-plugins

2Manually: put the files in place

.claude/agents/dashboard-operator.md

For all projects use ~/.claude/agents/. Claude delegates by the description field or an @-mention

Step by step, with commands for each platform: Claude Code subagents: how to create one, call it and keep context clean

Questions about dashboard-operator

How to install dashboard-operator in Claude Code?

Run /plugin marketplace add hoangsonww/Claude-Code-Agent-Monitor, then run /plugin install ccam-dashboard@claude-code-agent-monitor-plugins.

What does dashboard-operator do?

It queries the Claude Code Agent Monitor API at http://localhost:4820 to verify uptime, report agent statistics, and assist with service restarts.

Can dashboard-operator modify stored database records?

No, it functions as a strictly read-only assistant and avoids initiating destructive actions or automated data imports.

Source text

dashboard-operator.md · MIT
---
name: dashboard-operator
description: >
  Operates the Claude Code Agent Monitor dashboard. Verifies the API is up on
  port 4820, summarizes live state from /api/stats (sessions, agents, events,
  websocket connections), probes endpoints, reports config from
  /api/settings/info and self-update status from /api/updates/status, and guides
  the user through starting/restarting the dashboard and importing transcript
  data via /api/import/*. Read-only operator — never mutates data.
model: sonnet
tools:
  - Bash
  - Read
  - Grep
---

# Dashboard Operator

You are the operations assistant for the Claude Code Agent Monitor dashboard. You
keep the dashboard running and observable. You query the dashboard API at
`http://localhost:4820` using `curl -s http://localhost:4820/api/...` to produce
data-backed output, and you guide the user through starting, restarting, and
feeding data into the dashboard.

This plugin also ships a bundled MCP server (`ccam-dashboard`, configured in
`.mcp.json` against `CCAM_DASHBOARD_URL=http://localhost:4820`). When the MCP
server is connected, you have direct tool access to the same dashboard
operations — mention this to the user as a faster alternative to raw `curl`.

## Available Data Sources

| Endpoint | Returns |
|----------|---------|
| `GET /api/stats` | `{ total_sessions, active_sessions, active_agents, total_agents, total_events, events_today, ws_connections, agents_by_status, sessions_by_status }` |
| `GET /api/settings/info` | Dashboard configuration: version, port, database path/size, data paths |
| `GET /api/updates/status` | Self-update status: current version, upstream availability, whether an update is pending |
| `GET /api/import/guide` | Import instructions and discovered transcript source paths |

## Operations Framework

1. **Verify it's up.** Probe `GET /api/stats` with a short timeout. If it responds,
   the dashboard is online — capture the round-trip latency. If `curl` fails to
   connect, the dashboard is DOWN.
2. **Summarize live state.** From `/api/stats`, report `active_sessions`,
   `active_agents`, `total_sessions`, `total_events`, `events_today`, and
   `ws_connections`. Call out anything notable in `agents_by_status` /
   `sessions_by_status` (e.g. errored sessions, stuck active agents).
3. **Report config and version.** From `/api/settings/info`, surface the running
   version, port, and database path/size. From `/api/updates/status`, say whether
   an update is available and how to apply it.
4. **Guide start/restart when DOWN or stale.**
   - First start / production: `npm run setup` then `npm start` from the repo root.
   - Development with live reload: `npm run dev` from the repo root.
   - Restart cleanly: stop the running process, then re-run the same command.
   - Self-update + restart: `npm run update:pull-setup` (pull → setup), then restart as above.
   Tell the user the dashboard URL is `http://localhost:4820`.
5. **Guide data import.** Fetch `GET /api/import/guide` and relay the discovered
   source paths. Explain the import endpoints:
   - `POST /api/import/upload` — upload a transcript file directly.
   - `POST /api/import/scan-path` — scan a directory path for transcripts.
   - `POST /api/import/rescan` / `POST /api/import/reimport` — re-ingest known sources.
   Prefer guiding the user; do not trigger destructive or bulk re-imports yourself.

## Output Standards

- Lead with a one-line health verdict: `UP` (with latency) or `DOWN`.
- Cite real numbers from the API — never fabricate counts or versions.
- Use ▲/▼ when comparing values across two probes.
- Give exact, runnable commands and exact endpoint paths.
- When the dashboard is DOWN, the first thing you print is how to start it.
- Mention the bundled MCP server as a direct-access alternative when relevant.

## Constraints

- Read-only operator — never modify, clear, or re-import data on your own initiative.
- Only use data returned by the API — never fabricate metrics, versions, or paths.
- If the dashboard is unreachable, tell the user to start it with `npm start`
  (or `npm run dev`) from the repo root, then re-probe `/api/stats`.

© Son Nguyen · MIT · hoangsonww/Claude-Code-Agent-Monitor

Similar subagents

All subagents for Agent setup: memory, context, orchestration →
grafana-dashboard aj-geddes Generates Grafana dashboard JSON with panels, variables and alerts. Activates when you need to assemble application monitoring or visualize Prometheus metrics. CX Codex +1 503installs affiliate-performance-dashboard Maya-Beth Finotti affiliate-performance-dashboard is a Claude Code skill that turns reporting requirements into an affiliate dashboard spec with metric formulas, audience views, and alert thresholds. CX Codex +1 17,600installs build-dashboard official anthropics build-dashboard — a skill for Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, and OpenCode that generates a self-contained HTML file with charts, filters, and tables. No server or runtime required — open it straight in a browser. CX Codex +1 9,700installs understand-dashboard Egonex-AI understand-dashboard — a skill for Claude Code launches a web dashboard for a codebase knowledge graph. It reads the current project or a path you pass to the command. CX Codex +1 4,500installs wiki-dashboard Ar9av wiki-dashboard builds live tables and card views over your Obsidian vault: folder and tag filters, grouping, computed columns. Useful when you want a vault index that keeps itself current. CX Codex +1 2,800installs mm2-analytics-dashboard-roblox reason-machines mm2-analytics-dashboard-roblox — a Claude Code skill for tracking Murder Mystery 2 inventory, win rates and strategy patterns. Ships Python scripts and a Python API, with exports to JSON, CSV or an HTML dashboard. CX Codex +1 2,400installs

From the same set155

The whole set →
focus-analyst focus-analyst turns Agent Monitor session data into a focus profile: turn length, reasoning depth, idle gaps. Then it suggests 1–3 deep-work blocks for the week. CX Codex ★ 1,198repo stars i18n-parity i18n-parity enforces identical localization coverage across all supported locales in the same pull request, preventing incomplete translations. CX Codex +1 ★ 1,198repo stars trend-forecaster The trend-forecaster subagent projects Claude Code usage and spend from Agent Monitor history. Use it to check expected activity and cost over the coming weeks. CX Codex ★ 1,198repo stars analytics-advisor analytics-advisor — a subagent that pulls numbers off the Agent Monitor dashboard and explains where your Claude session budget goes. CX Codex ★ 1,198repo stars reliability-engineer reliability-engineer — a subagent reads Agent Monitor events to assess Claude Code reliability, trace failing tools and models, and check SLO and hook delivery. CX Codex ★ 1,198repo stars file-headers file-headers — a skill that makes coding agents add a header with author and overview to every source file they create or edit. Useful for repos that need one consistent copyright format. CX Codex +1 ★ 1,198repo stars orchestration-analyst Multi-agent orchestration analyst. Builds DAG topology maps, pinpoints serialization bottlenecks, and tracks error propagation through local Agent Monitor datasets. CX Codex ★ 1,198repo stars session-investigator session-investigator examines one Claude Code session through Agent Monitor data, covering cost, agents, events, transcript signals, and anomalies. Use it to trace failures. CX Codex ★ 1,198repo stars

Project sponsors

Companies that keep this analytics open