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.5 KiB
description, argument-hint
| description | argument-hint |
|---|---|
| Summarize the workflow intelligence for a session — stats, complexity, and top patterns. | [session-id] |
Summarize the Agent Monitor workflow intelligence for a session from http://localhost:4820.
The session id is $ARGUMENTS. If empty, fetch curl -s 'http://localhost:4820/api/sessions?limit=1' and use the most recent session, stating which id you picked. If the dashboard is unreachable, tell the user to start it with npm start from the repo root.
Fetch the workflow intelligence:
curl -s http://localhost:4820/api/workflows/$ARGUMENTS
This returns 11 datasets: stats, orchestration, toolFlow, effectiveness, patterns, modelDelegation, errorPropagation, concurrency, complexity, compaction, cooccurrence.
Print, concisely:
- Header — session id, total agents, max depth, and total tool calls (from
stats/orchestration). - Complexity — the numeric
complexityscore and what drives it (depth, breadth, tool diversity). - Top patterns — up to 5 recurring sequences from
patterns, each assequence ×frequency, sorted by frequency descending. - Quick signals — one line each: concurrency lane count (
concurrency), subagent success rate (effectiveness), and total errors with origin depth (errorPropagation).
Keep it terse — this is a one-shot. Cite only numbers returned by the API; for deeper analysis point the user at the dag-map, delegation-audit, concurrency-report, or error-propagation skills.