Files
nntrivi2001 17d56d0e01 refactor!: rebrand CCAM to AgentHub
Clean break, no compatibility alias. Renames the product name, the CLI
binary (`ccam` -> `agenthub`), the env var prefix (`CCAM_` ->
`AGENTHUB_`), the Prometheus metric namespace (`ccam_*` ->
`agenthub_*`), the tmux session prefix (`ccam-lane-<id>` ->
`agenthub-lane-<id>`), the per-repo runtime profile directory
(`.ccam/profile` -> `.agenthub/profile`), the lanes state root
(`~/.claude/ccam-lanes` -> `~/.claude/agenthub-lanes`), the bundled
plugins (`plugins/ccam*` -> `plugins/agenthub*`) and their slash
commands (`/ccam-doctor` -> `/agenthub-doctor`, `/ccam:*` ->
`/agenthub:*`).

Because there is no alias, an existing install has to be updated by
hand: rename its `.ccam/profile` directory and any `CCAM_*` variables,
and reinstall the plugin under its new name.

Two other name families are deliberately left alone here, since they are
not just strings: the `Claude-Code-Monitor` repository/marketplace name,
and the `agent-dashboard` npm package plus its `~/.claude/agent-dashboard`
runtime directory, which holds the live database and needs a migration
rather than a rename.

Verified: server 1406/1406, client 459/459, `grep -i ccam` clean across
tracked files, `openapi.yaml` regenerated (95 paths, unchanged count).
2026-09-07 12:09:15 +07:00

1.3 KiB

description
description
Quick connectivity + health probe of the Agent Monitor dashboard.

Run a fast health probe against the Agent Monitor dashboard at http://localhost:4820. Do two checks and print OK / FAIL for each.

  1. API + stats — fetch core stats:

    curl -s -o /dev/null -w '%{http_code}' http://localhost:4820/api/stats
    curl -s http://localhost:4820/api/stats
    

    PASS if HTTP 200 and the body is valid JSON. From the body, surface total_sessions, active_sessions, total_events, and events_today.

  2. Self-update status — confirm the update subsystem responds:

    curl -s -o /dev/null -w '%{http_code}' http://localhost:4820/api/updates/status
    curl -s http://localhost:4820/api/updates/status
    

    PASS if HTTP 200 and valid JSON. Surface whether an update is available and the current vs latest version if present.

Print a compact report, one line per check:

Agent Monitor Doctor
  API /api/stats ............ OK  (sessions=12 active=1 events=3480 today=57)
  /api/updates/status ....... OK  (up to date — v1.x.x)

Overall: OK (2/2)

Use ✅ OK / ❌ FAIL markers. If any curl fails to connect (non-200 or no response), mark that check FAIL and end with: "Dashboard unreachable — start it with npm start from the repo root." Keep it to the report only; no extra prose.