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).
59 lines
2.5 KiB
Markdown
59 lines
2.5 KiB
Markdown
---
|
|
description: >
|
|
Walk a Claude Code session transcript turn-by-turn from Agent Monitor data,
|
|
summarizing each user, assistant, and tool message in order so a long conversation
|
|
can be reviewed quickly. Anchors the recap to the session header (model, cost,
|
|
turn_count). Use when reviewing what was actually said and done in a conversation.
|
|
---
|
|
|
|
# Transcript Replay
|
|
|
|
Replay a session transcript one turn at a time with a concise summary of each message.
|
|
|
|
## Input
|
|
|
|
The user provides: **$ARGUMENTS**
|
|
|
|
- A **session ID** to replay, or
|
|
- "latest" / "last" for the most recent session.
|
|
- Optionally a turn range (e.g. `1-10`) or `errors` to focus on tool failures.
|
|
|
|
## Data Sources
|
|
|
|
| Endpoint | Returns |
|
|
|----------|---------|
|
|
| `GET /api/sessions/:id/transcript` | ordered transcript messages: role (user / assistant / tool), content, tool_name and tool result where applicable, timestamps |
|
|
| `GET /api/sessions/:id` | session header: status, model, cwd, started_at, ended_at, cost, metadata (thinking_blocks, turn_count, total_turn_duration_ms) |
|
|
|
|
## Report Sections
|
|
|
|
### 1. Header
|
|
`GET /api/sessions/:id`. Print id, model, cwd basename, status, turn_count,
|
|
thinking_blocks, total_turn_duration_ms, and cost in one block.
|
|
|
|
### 2. Turn-by-turn walk
|
|
`GET /api/sessions/:id/transcript`. Iterate messages in order. For each turn emit
|
|
one compact entry:
|
|
- **user** — the request in one sentence (quote the literal ask only if short).
|
|
- **assistant** — the decision / action taken, plus which tools it invoked.
|
|
- **tool** — the tool name and a one-line result (success value or the error text);
|
|
do not paste large tool payloads.
|
|
|
|
Group an assistant message with the tool calls it triggered so each "turn" reads as
|
|
intent → action → result.
|
|
|
|
### 3. Thread highlights
|
|
After the walk, pull out: the original goal, the key turning points, any tool
|
|
failures or retries, and how the session ended (resolved / errored / abandoned).
|
|
|
|
## Output
|
|
|
|
A numbered turn list (`Turn N — <role>: <one-line summary>`), grouped intent →
|
|
action → result, preceded by the header block and followed by the highlights.
|
|
Truncate any quoted content past ~200 chars with `…`. Currency as USD to 4 decimal
|
|
places. Summarize faithfully — never invent message content that is not in the
|
|
transcript. If the transcript endpoint returns empty, say the session has no stored
|
|
transcript (it may predate transcript capture or need a reimport) rather than
|
|
fabricating turns. If the dashboard is unreachable, tell the user to start it with
|
|
`npm start` from the repo root.
|