Files

T

nntrivi2001 57dc91585d feat: Claude Code Monitor — lanes, pipelines and a merged workspace

Internal SmartGift build of a Claude Code monitoring dashboard.

Lanes: a durable unit of parallel agent work, one per working directory,
tracked across session restarts. Managed lanes are git worktrees the
dashboard provisions and can reset or remove behind a three-check destroy
guard and a counted preflight; adopted lanes are directories you already
own and are never destroyable.

Pipelines: a lane moves through pipeline stages. A stage the agent declares
with evidence renders green; a stage inferred from the tool-event stream
renders dashed amber and never counts as done. Detection is forward-only
within a 30-minute window, and never writes the declared stage.

Workspace: one page at /run with a lane grid, the selected lane's pipeline,
and a full Claude console behind a disclosure.

2026-07-30 14:39:03 +07:00

2.5 KiB

Raw Blame History

description

description
Quick dashboard health and status overview — checks the Agent Monitor API (port 4820), reports session/agent/event counts from /api/stats, confirms WebSocket connectivity, validates hook configuration in ~/.claude/settings.json, and shows data freshness (last event timestamp). Use to verify the monitoring system is operational.

Dashboard Status

Quick status check on the Claude Code Agent Monitor dashboard.

Input

The user provides: $ARGUMENTS

Options: empty (default: full status), "quick" (API only), "verbose" (include endpoint details).

Data Sources

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)

Status Report

1. API Server

Reachable at http://localhost:4820? Response time?
If unreachable: suggest npm start from the project directory

2. System Counts

From /api/stats:

Total sessions tracked (total_sessions)
Active agents currently running (active_agents)
Total events ingested (total_events)
Events today (events_today)
WebSocket connections (ws_connections)

3. Data Freshness

From latest event:

Time since last event ingested
If >1 hour: warn about possible hook disconnect

4. Hook Status

Check ~/.claude/settings.json for configured hooks:

Expected: PreToolUse, PostToolUse, Stop, SubagentStop, Notification, SessionStart, SessionEnd
Report which hooks are present vs missing

5. Dashboard Info

From /api/settings/info:

Dashboard version
Database path and size
Configured port

Output Format

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         ║
╚══════════════════════════════════════╝

2.5 KiB Raw Blame History