Activity
Activity Overview is the time side of the picture: how much you use Claude Code, when, and how your sessions are shaped. It’s personal, updates live, and pairs with Productivity (what you produced) and Telemetry (the raw numbers).
The four tiles
Section titled “The four tiles”- Sessions — how many Claude Code sessions you ran, with the request count.
- Active Time — time you were actually coding in the CLI, not wall-clock time that includes idle gaps.
- Avg Session — the average session length (the subtitle also gives the median).
- API Equiv. Cost — the total API-equivalent cost of your usage for the range; the subtitle breaks it down per session.
When and how you work
Section titled “When and how you work”- Activity Heatmap — a day × hour grid of your sessions; page it week by week to find your peak coding windows.
- Daily Sessions & Requests — requests per day with API cost overlaid. Fewer requests per session usually means tighter prompting.
- Session Efficiency — a chart with three series: Avg Duration, LLM Time (the model working), and Idle Time (waiting or thinking). Shorter sessions with less idle time point to a tighter workflow.
- Errors & Retries — errors per day; a downward trend means cleaner runs.
Active Time
Section titled “Active Time”A section further down breaks your time down more finely:
- User Time and CLI Time — how your active time splits between you driving and the CLI working, each as a share of the total.
- Event Timeline — a scatter of your activity (user, CLI, mixed).
- Active Time Trend and User vs CLI Time — the trend over time and the split, each with its own hour / day / week / month granularity.
A Live indicator shows how fresh the data is; refresh manually or let it update on its own.