Skip to content

Activity

Review session activity and estimated time use.

Open Insights → Activity to review when you used Claude Code or Codex and how recorded session time is distributed.

  1. Choose the date range (the last 30 days by default) and read the Sessions, Active time, Average session, and API-converted cost figures.
  2. Use the activity heatmap to find your busiest weekdays and hours. It shows one week at a time; use the previous and next week controls to move.
  3. Compare daily sessions and requests, session efficiency (average duration, LLM time, and idle time), and errors and retries.
  4. Inspect the active-time split between user time and CLI time, the trend, and the event timeline for a period you want to understand.

Sessions counts the sessions that had activity in the period. When the period includes time for which sessions were not counted, the card says “Not counted for part of this period” and the heatmap says “Session count not available”. A missing count is not zero.

Active time is estimated from observed activity: each gap between two events counts for at most five minutes. User time and CLI time are classifications of that activity, not a timesheet or a direct observation of everything you did. A shorter session or fewer requests does not establish better prompt writing.

Use Sessions to find related work, Telemetry for request and error detail, and Productivity for captured changes.

Use the refresh control and its aggregation time to check how current a value is. If a value is missing, confirm the date range and collection status. Do not infer no work from absent telemetry.