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).
997 B
997 B
description, argument-hint
| description | argument-hint |
|---|---|
| List the top N most expensive Claude Code sessions by inline cost. | [N] |
List the most expensive Claude Code sessions from the Agent Monitor dashboard.
N = $ARGUMENTS (default 10 if empty).
Fetch the session list (each session carries an inline cost field from bulk pricing):
curl -s "http://localhost:4820/api/sessions?limit=200"
Then:
- Sort sessions by
costdescending. - Print the top
Nas a numbered list, one line each:<rank>. $<cost to 4dp> — <model> — <cwd basename or id> — <started_at> - After the list, print the summed cost of the top N and what percent that is of the summed cost of all returned sessions.
Currency as USD to 4 decimal places. Skip sessions with no/zero cost only if it would otherwise pad the list past meaningful entries — otherwise include them. Keep it terse, no extra commentary.
If the dashboard is unreachable, tell the user to start it with npm start from the repo root.