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.3 KiB
1.3 KiB
description
| description |
|---|
| One-screen inventory of skills, agents, commands, MCP servers, and hooks counts. |
Print a one-screen inventory of the user's Claude Code config from the Agent
Monitor Config Explorer at http://localhost:4820. Fetch the overview once:
curl -s http://localhost:4820/api/cc-config/overview
From counts, surface just the five core surfaces:
- skills —
counts.skills.user + counts.skills.project - agents —
counts.agents.user + counts.agents.project - commands —
counts.commands.user + counts.commands.project - mcp —
counts.mcpServers.user + counts.mcpServers.project - hooks —
counts.hooks.user + counts.hooks.project + counts.hooks["project-local"]
Print a single compact block with the total for each, plus the user/project split in parentheses where it applies:
Config Inventory
Skills ... 25 (user 22 / project 3)
Agents ... 8 (user 7 / project 1)
Commands . 14 (user 14 / project 0)
MCP ...... 6 (user 5 / project 1)
Hooks .... 7 (user 7 / project 0 / local 0)
Cite only the numbers the API returned — never fabricate counts. If the
dashboard is unreachable, say so and tell the user to start it with npm start
from the repo root. Keep it to the block only; no extra prose.