Files
AgentHub/plugins/agenthub-devtools/skills/event-trace/SKILL.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

3.0 KiB

description
description
Trace the full event chain for one Claude Code session into an ordered timeline of every event type with tool_name and summary, highlighting gaps, out-of-order events, and failures. Reads /api/events?session_id= and /api/sessions/:id from the Agent Monitor dashboard. Use when debugging what a session actually did, step by step.

Event Trace

Build a chronological, annotated event timeline for a single session.

Input

The user provides: $ARGUMENTS

This is a session ID. It may also be:

  • latest / last — trace the most recently updated session
  • errors — trace the most recent session whose status is error

Data Sources

Endpoint Returns
GET /api/sessions?limit=N session list (used to resolve latest/errors and the target id)
GET /api/sessions/:id full session detail (status, model, cwd, started_at, ended_at, cost, nested agents + events)
GET /api/events?session_id=X the ordered event stream: event_type, tool_name, summary, data, timestamp

Report Sections

1. Resolve the session

If $ARGUMENTS is a raw id, use it. If latest/last, call GET /api/sessions?limit=1. If errors, call GET /api/sessions?limit=10&status=error and pick the newest. Confirm the id resolves via GET /api/sessions/:id; if not, report it as missing and stop.

2. Session header

From GET /api/sessions/:id: id, status, model, cwd, started_at → ended_at, total duration, cost (USD to 4 decimals), and counts (events, agents).

3. Ordered timeline

From GET /api/events?session_id=X, list every event in timestamp order. One row per event:

| # | time | Δ since prev | event_type | tool_name | summary |

Cover all event types present: SessionStart, PreToolUse, PostToolUse, Stop, SubagentStop, Compaction, APIError, TurnDuration, Notification, SessionEnd.

4. Gap & failure highlights

Annotate the timeline:

  • Gaps: any Δ > 30s between consecutive events — mark ⏳ and note the wait.
  • Unpaired tool calls: a PreToolUse with no matching PostToolUse (same tool_name, next in stream) — mark ⚠️ "no completion recorded".
  • Failures: APIError events and PostToolUse whose summary/data indicates an error — mark ❌ with the error text.
  • Compaction: mark ♻️ and note it resets the visible token baseline.
  • Missing bookends: no SessionStart at the head or no Stop/SessionEnd at the tail of an ended session — mark 🚩.

5. Verdict

One line: CLEAN, GAPS DETECTED, or FAILURES PRESENT — with the count of each flag type and the single most likely thing to investigate next.

Output

  • Markdown timeline table, events in strict timestamp order.
  • Status glyphs inline: ✅ ok, ❌ error, ⚠️ warning/unpaired, ⏳ gap, ♻️ compaction, 🚩 missing bookend.
  • Currency in USD to 4 decimals.
  • Cite only event data returned by the API — do not invent timestamps or summaries.
  • If the dashboard is unreachable, tell the user to start it with npm start from the repo root.