Files
AgentHub/plugins/agenthub-insights/commands/compare.md
T
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.8 KiB
Raw Blame History

description, argument-hint
description argument-hint
Compare two sessions side-by-side with cost and workflow deltas [sessionA] [sessionB]

Compare the two sessions in $ARGUMENTS (first id = Session A, second id = Session B) side-by-side using the Agent Monitor dashboard. If fewer than two ids are given, ask for both.

  1. Fetch cost for each, in parallel:

    • curl -s http://localhost:4820/api/pricing/cost/<sessionA>
    • curl -s http://localhost:4820/api/pricing/cost/<sessionB> Each returns { total_cost, breakdown:[{ model, input_tokens, output_tokens, cache_read_tokens, cache_write_tokens, cost, matched_rule }] }.
  2. Fetch workflow intelligence for each:

    • curl -s http://localhost:4820/api/workflows/<sessionA>
    • curl -s http://localhost:4820/api/workflows/<sessionB> Use stats (tool/event/agent counts), complexity (score), effectiveness (subagent success), compaction (impact), and errorPropagation.
  3. Print a side-by-side comparison table with a delta column (B − A):

    • Total cost (USD, 4 decimals) and Δ% .
    • Tokens: input, output, cache_read, cache_write (sum the breakdown per session).
    • Cache hit rate = cache_read / (cache_read + input).
    • Tool count, event count, agent count (from stats).
    • Complexity score (from complexity).
    • Subagent success rate (from effectiveness) and compaction count (from compaction).

Output rules: one row per metric with columns Session A | Session B | Δ; use ▲ when B is higher and ▼ when lower; currency in USD to 4 decimals; rates as percentages to 2 decimals. End with a one-line verdict on which session was cheaper/leaner and the main driver. Cite only fields the API returned — never fabricate. If a session id is unknown or the dashboard is unreachable at http://localhost:4820, say so and tell the user to start it with npm start from the repo root.