Render an ordered timeline of one Claude Code session's events (every event type) with per-event durations and tool names, reconstructed from Agent Monitor data. Pairs PreToolUse with PostToolUse to compute tool durations and surfaces gaps, errors, and compaction points. Use when reconstructing what happened in a session step by step.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
설치 방법 보기설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.
Reconstruct the chronological event timeline of a single Claude Code session.
The user provides: $ARGUMENTS
| Endpoint | Returns |
|---|---|
GET /api/sessions/:id | session header: status, model, cwd, started_at, ended_at, cost, metadata (thinking_blocks, turn_count, total_turn_duration_ms) — and nested events |
GET /api/events?session_id=X | the full event stream: event_type (PreToolUse, PostToolUse, Stop, SubagentStop, SessionStart, SessionEnd, Notification, Compaction, APIError, TurnDuration), tool_name, summary, data, timestamp |
If "latest", GET /api/sessions?limit=1 to get the id, then GET /api/sessions/:id.
Print a one-line header: id, status, model, cwd basename, started_at → ended_at,
turn_count, total_turn_duration_ms, cost.
GET /api/events?session_id=X. Sort strictly by timestamp. For each event emit a
row with: relative offset from started_at (e.g. +00:03.412), event_type,
tool_name (when present), and a one-line summary.
Pair each PreToolUse with its matching PostToolUse (same tool_name, next
occurrence) and show the tool's wall-clock duration. For TurnDuration events use
the recorded duration directly. Flag any PreToolUse with no matching PostToolUse
as unclosed.
Mark APIError (❌), Compaction (⚠️ context compressed), SubagentStop
(subagent finished), Notification (ℹ️), and any timeline gap > 30s between
consecutive events as an idle window.
Event count by type, total tool time vs. session wall time, and the longest single tool call.
A Markdown table — offset | event_type | tool_name | duration | summary — in
strict timestamp order, preceded by the header line and followed by the tallies.
Durations in ms or mm:ss.mmm; currency as USD to 4 decimal places. Never invent a
duration when a PostToolUse is missing — label it unclosed. If the dashboard is
unreachable, tell the user to start it with npm start from the repo root.
아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.
로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.
아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.
Inspect fired CCAM alerts and manage alert rules for token thresholds, event patterns, inactivity, and status duration. Use when acknowledging alerts, creating or editing a rule, checking cooldowns, or connecting alert rules to webhook targets.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Identify anomalous sessions using Agent Monitor data — cost outliers from the pricing engine, token anomalies (cache miss spikes, compaction baseline surges), unusual event type ratios (PreToolUse/PostToolUse gaps, APIError clusters), behavioral deviations from workflow intelligence (complexity score outliers, error propagation anomalies), and sessions with abnormal metadata (extreme turn_count, high thinking_blocks, zero turn_duration).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Produce a detailed report on APIError events from Agent Monitor data — counts over time, which sessions and models are affected, and the likely root cause (rate limits, overload/529, or context-window pressure) inferred from each event's summary and data payload. Use when API errors spike or when you need to explain why requests are failing.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Benchmark one session (or a small recent set) against the rolling average using Agent Monitor data — cost, total tokens, tool count, and workflow complexity score — and report where each metric lands as a percentile of the population. Tells you whether a session was normal, cheap, or an outlier. Use when judging whether a session was typical or out of band.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Define a spend budget for Claude Code and, optionally, create a cost alert rule that fires when usage crosses the limit, via POST /api/alerts/rules on the Agent Monitor dashboard. Reads current spend from /api/pricing/cost to size the budget sensibly and explains every rule field before writing. Use when setting a spend limit or wiring up a budget guardrail.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Analyze prompt-cache effectiveness for Claude Code usage from the Agent Monitor dashboard — cache hit rate (total_cache_read / (total_cache_read + total_input)), cache_write vs cache_read reuse, cache-read vs cache-write spend, and the sessions with the poorest reuse. Pulls token totals from /api/analytics, per-session detail from /api/sessions, and dollar splits from /api/pricing/cost. Use when diagnosing cache spend or deciding whether prompt caching is paying off.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.