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

3.1 KiB

Raw Blame History

description

description
Run comprehensive health checks on the Claude Code Agent Monitor system. Validates dashboard API, database, WebSocket, hooks, and disk usage. Use to verify the monitoring setup is working correctly.

Health Check

Run a comprehensive health check on the Agent Monitor system.

Input

The user provides: $ARGUMENTS

This may be:

"full" or empty (default: run all checks)
"quick" for a fast connectivity check
"deep" for extended checks including database integrity

Procedure

Run health checks in this order:

1. API Health

curl -sf http://localhost:4820/api/health

Verify HTTP 200 response
Check response time (<500ms expected, <1000ms acceptable)
Confirm JSON response body

2. Database Health

curl -sf http://localhost:4820/api/stats

Verify stats endpoint returns valid data
Check that counts are non-negative integers
Verify database file exists and has reasonable size

3. WebSocket Health

Check that the WebSocket server is listening
Verify WebSocket upgrade is supported on the dashboard port

4. API Endpoint Validation

Test each major endpoint:

curl -sf http://localhost:4820/api/sessions?limit=1
curl -sf http://localhost:4820/api/events?limit=1
curl -sf http://localhost:4820/api/analytics
curl -sf http://localhost:4820/api/pricing
curl -sf http://localhost:4820/api/settings/info

5. Hook Integration

Verify hook handler script exists
Check hooks are configured in ~/.claude/settings.json
Verify the handler script targets the correct dashboard URL

6. Disk & Resource Usage (deep mode only)

Database file size
Log file sizes (if any)
Available disk space
Node.js process memory usage (if accessible)

7. Data Freshness

Time since last event ingested
Time since last session created
Check for stale active sessions (active but no events in >1 hour)

Output Format

Present as a system health dashboard:

╔══════════════════════════════════════════════╗
║   AGENT MONITOR HEALTH CHECK                ║
║   Timestamp: 2025-04-11 12:00:00 UTC        ║
╠══════════════════════════════════════════════╣
║                                              ║
║   API Server ............ ✅ OK (45ms)       ║
║   Database .............. ✅ OK (2.4 MB)     ║
║   WebSocket ............. ✅ OK              ║
║   API Endpoints ......... ✅ 6/6 passing     ║
║   Hook Integration ...... ⚠️ 5/7 hooks      ║
║   Data Freshness ........ ✅ 3m ago          ║
║                                              ║
║   Overall: HEALTHY (5/6 checks passed)       ║
║                                              ║
╚══════════════════════════════════════════════╝

For any non-passing check, include detailed explanation and remediation steps below the dashboard.

3.1 KiB Raw Blame History