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, argument-hint
| description | argument-hint |
|---|---|
| Export Agent Monitor data (sessions/events/analytics/costs/all) as json/csv/md. | [sessions|events|analytics|costs|all] [json|csv|md] |
Export Agent Monitor data using the dashboard export endpoint. Arguments:
$ARGUMENTS — the first token is the data type, the second is the format.
type∈sessions | events | analytics | costs | all(defaultall)format∈json | csv | md(defaultjson)
Set TYPE and FORMAT from the args (apply the defaults if missing), then run:
TYPE="${1:-all}"; FORMAT="${2:-json}"
curl -s "http://localhost:4820/api/settings/export?type=${TYPE}&format=${FORMAT}" \
-o "agenthub-export-${TYPE}.${FORMAT}"
Then:
- Confirm the file was written and report its absolute path and byte size.
- Preview the result: for
csv/mdprint the first ~15 lines; forjsonprint a pretty-printed head (e.g.head -c 1500or the first array element plus the record count). - Print a one-line summary:
Exported <type> as <format> → <path> (<N> records / <bytes>).
If the curl returns a non-200 or an error body, do not claim success — print the
error and remind the user to start the dashboard with npm start from the repo
root. Do not delete or overwrite any existing data; this command only reads via
the export endpoint and writes a new export file.