Quick dashboard health and status overview — checks the Agent Monitor API (port 4820), reports session/agent/event counts from /api/stats, confirms WebSocket connectivity, reads the redacted hook status returned by /api/settings/info, and shows data freshness (last event timestamp). Use to verify the monitoring system is operational.
The English summary is being prepared. Showing the original description.
Run score Not tested
See how to installReview the instructions the agent will receive before you install.
Quick status check on the Claude Code Agent Monitor dashboard.
The user provides: $ARGUMENTS
Options: empty (default: full status), "quick" (API only), "verbose" (include endpoint details).
| Endpoint | Returns |
|---|---|
GET /api/health | HTTP 200 if API is running |
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, data paths |
GET /api/events?limit=1 | Most recent event (for freshness check) |
http://localhost:4820? Response time?npm start from the project directoryFrom /api/stats:
total_sessions)active_agents)total_events)events_today)ws_connections)From latest event:
Use /api/settings/info → hooks for configured hook names:
From /api/settings/info:
Compact status card:
╔══════════════════════════════════════╗
║ AGENT MONITOR STATUS ║
╠══════════════════════════════════════╣
║ API: ✅ Online (42ms) ║
║ Sessions: 127 tracked ║
║ Events: 4,892 ingested ║
║ Hooks: 7/7 configured ║
║ Last Event: 3 minutes ago ║
╚══════════════════════════════════════╝
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Inspect fired CCAM alerts and manage alert rules for token thresholds, event patterns, inactivity, and status duration. Use when acknowledging alerts, creating or editing a rule, checking cooldowns, or connecting alert rules to webhook targets.
The English summary is being prepared. Showing the original description.
Identify anomalous sessions using Agent Monitor data — cost outliers from the pricing engine, token anomalies (cache miss spikes, compaction baseline surges), unusual event type ratios (PreToolUse/PostToolUse gaps, APIError clusters), behavioral deviations from workflow intelligence (complexity score outliers, error propagation anomalies), and sessions with abnormal metadata (extreme turn_count, high thinking_blocks, zero turn_duration).
The English summary is being prepared. Showing the original description.
Produce a detailed report on APIError events from Agent Monitor data — counts over time, which sessions and models are affected, and the likely root cause (rate limits, overload/529, or context-window pressure) inferred from each event's summary and data payload. Use when API errors spike or when you need to explain why requests are failing.
The English summary is being prepared. Showing the original description.
Benchmark one session (or a small recent set) against the rolling average using Agent Monitor data — cost, total tokens, tool count, and workflow complexity score — and report where each metric lands as a percentile of the population. Tells you whether a session was normal, cheap, or an outlier. Use when judging whether a session was typical or out of band.
The English summary is being prepared. Showing the original description.
Define a spend budget for Claude Code and, optionally, create a cost alert rule that fires when usage crosses the limit, via POST /api/alerts/rules on the Agent Monitor dashboard. Reads current spend from /api/pricing/cost to size the budget sensibly and explains every rule field before writing. Use when setting a spend limit or wiring up a budget guardrail.
The English summary is being prepared. Showing the original description.
Analyze prompt-cache effectiveness for Claude Code usage from the Agent Monitor dashboard — cache hit rate (total_cache_read / (total_cache_read + total_input)), cache_write vs cache_read reuse, cache-read vs cache-write spend, and the sessions with the poorest reuse. Pulls token totals from /api/analytics, per-session detail from /api/sessions, and dollar splits from /api/pricing/cost. Use when diagnosing cache spend or deciding whether prompt caching is paying off.
The English summary is being prepared. Showing the original description.