Files
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.4 KiB
Raw Permalink Blame History

description, argument-hint
description argument-hint
Summarize one Agent Monitor session by id — header plus a concise transcript recap. [session-id]

Produce a concise recap of one Claude Code session tracked by the Agent Monitor.

The session id is $ARGUMENTS. If empty, resolve the latest: curl -s "http://localhost:4820/api/sessions?limit=1" and use its id.

Fetch the session header and its transcript:

curl -s "http://localhost:4820/api/sessions/$ARGUMENTS"
curl -s "http://localhost:4820/api/sessions/$ARGUMENTS/transcript"

The first returns the session detail (status, model, cwd, started_at, ended_at, cost, metadata: turn_count, thinking_blocks, total_turn_duration_ms). The second returns the ordered transcript messages (user / assistant / tool).

Then print, concisely:

  1. Header — one block: id · model · status · cwd basename · turn_count turns · $<cost to 4dp> · <started_at → ended_at>.
  2. Recap — 5–10 bullets walking the conversation in order: the user's goal, the key assistant actions and tools used, any tool failures, and how it ended. Summarize each message in one line; do not paste large payloads (truncate past ~200 chars with …).

Currency as USD to 4 decimal places. If the transcript is empty, say the session has no stored transcript rather than inventing turns. If the dashboard is unreachable, tell the user to start it with npm start from the repo root.