Every number in Usage Insights for Claude Code comes from a data catalog: 73 metrics, each with a definition, a source and the chart that fits it. The Catalog view puts that catalog next to the dashboard, and says which numbers the tool shows and which need data only an admin can reach.
Search the catalog
Open Catalog. Search by name, definition, source or chart, or filter to Me, Team, Telemetry or Shown here.
Shown here takes you to the view that shows the metric. Needs admin data marks the few that no local file can answer, such as time to first token or plugin inventory.
The rules behind it
The catalog follows a few rules, listed at the bottom of the view. Metadata over content: count and time things, never show prompt text in team views. Personal is private by default. Groups under five people are hidden. Every estimate says it is one.
Write events from any source
Not everything runs in Claude Code. The unified event schema is one JSON object per action, with a time, a pseudonymous user, a team, a surface, a model, tokens and cost:
A gateway or proxy in front of the Claude API, or your own app, can write these lines. Usage Insights for Claude Code reads them as .jsonl or as a JSON array, together with Claude Code folders, so one dashboard covers every source. Copy example copies the event shown.
Take the whole dashboard with you
Export has two full reports:
- Full report (.html): every view (Me, Capabilities, Team when there is one, Telemetry and the catalog) in one file that opens in any browser, offline, with nothing to install.
- Full report (PDF): the same, laid out on A4 landscape pages to read or print: a cover with the range and the source, each view starting on a new page, panels never cut in half, and a page number on every page. The print window opens; choose Save as PDF as the printer.
Both are made in your browser from data that never left your computer. They show your session titles under Recent work, so look through one before you pass it on.
Take the numbers elsewhere
Export also saves three data files: Events in the unified schema, a Summary with every number on every view as JSON, and a Daily table as CSV with prompts, sessions, tokens, cost, tool calls and errors per day, ready for a spreadsheet or a BI tool.
Use OpenTelemetry for a live dashboard
For a dashboard that updates by itself, Claude Code can export metrics to any OpenTelemetry collector. The Telemetry view lists the metric names, such as claude_code.cost.usage and claude_code.lines_of_code.count, with their attributes. Keep prompt and tool content off in that export, as this tool does.