nntrivi2001
17d56d0e01
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).
1.6 KiB
1.6 KiB
description
| description |
|---|
| Surface the top 3 data-backed insights about your Claude Code usage right now |
Produce the top 3 insights about Claude Code usage right now, each backed by real numbers from the Agent Monitor dashboard.
-
Fetch high-level state:
curl -s http://localhost:4820/api/stats→ total_sessions, active_sessions, active_agents, total_events, events_today, agents_by_status, sessions_by_status.curl -s http://localhost:4820/api/analytics→ tokens (total_input/total_output/total_cache_read/total_cache_write), tool_usage (top 20), daily_events (365d), daily_sessions (365d), event_types, avg_events_per_session, total_subagents.
-
Derive signal, citing exact field values:
- Cache hit rate =
total_cache_read / (total_cache_read + total_input). - Activity trend: compare the last 7 days of
daily_sessions/daily_eventsagainst the prior 7. - Concentration: the single most-used tool and most-frequent
event_type, with its share of the total. - Error pressure:
APIErrorshare of events; subagent fan-out viatotal_subagentsandavg_events_per_session.
- Cache hit rate =
-
Pick the 3 most decision-relevant findings (biggest cost lever, sharpest trend, or clearest anomaly). For each print:
- A one-line headline with the supporting number.
- Why it matters in one sentence.
- One concrete action.
Output rules: rank by impact (most important first); currency in USD to 4 decimals; rates as percentages to 2 decimals; use ▲/▼ for trend direction; cite only fields the API returned — never fabricate. If curl cannot reach http://localhost:4820, tell the user to start the dashboard with npm start from the repo root.