cctopOperator's manual

cctop / Panel guide / Events

§8EventsNoteThe newest line is at the bottom; f filters by kind.

Events

The chronological stream every other panel is built from: tool calls starting and finishing, hooks firing, permission prompts opening and closing, compactions, and notes cctop records about the session. Nothing here is aggregated — it's the raw timeline.

The timeline

reads as
20:41:17 perm Bash allowed (auto)
What it means
The other panels show you totals and rates; Events shows you the order things happened in. That's what you need to reconstruct why one particular turn was slow or expensive, rather than just knowing that it was. Each line is a time, a kind — tool, hook, perm, agent, compact, api, note, away, coach (a nudge fired, was acted on, expired or was snoozed), cost (a priced moment: a named cache miss, a cold write, a model switch, a loop fire) — and what happened.
What to do
Use it to find the exact moment things went sideways — a run of tool errors, a compaction, a long permission wait — then switch to the relevant numbered panel for the detail behind that moment.

Notes

reads as
20:41:39 note rate-limit 5h crossed 60 %
What it means
Lines cctop writes itself when a threshold is crossed: the context entering Claude Code's warn band, the 5-hour limit past 60, 80 or 95 %, the limit projected to run out before its reset, a tool running longer than a minute, an MCP server that exited, time spent on API retries, a turn that died on an API error, Claude waiting on you for half a minute, and the cache countdown while a question waits. Each also shows briefly as a toast, and with --notify the three critical ones reach your desktop.
What to do
Treat them as the moments worth a glance at the dashboard; the panel the note names has the detail.