Messages and tokens are what you put in. What matters is what came out: code you kept, commits, pull requests. The Me view shows both, and this lesson walks through it from the heatmap down.
When you work
Time-of-day pattern counts your prompts by weekday and hour, in your own time zone. Darker squares mean more prompts. Most people see a block in working hours; late-night columns and weekend rows show up at once.
Your highlights
Beside it, the Highlights card picks out a few lines for the range: your longest streak and when it ended, your busiest day, your biggest session with its title, your most-used skill, and capabilities you used for the first time.
What you produced
What I produced turns activity into outcomes:
- Outputs created: files Claude created, and for other sources artifacts, documents, decks and sheets
- Lines of code: lines added and removed by Claude's edits
- Commits & PRs:
git commitandgh pr createcommands that ran successfully - Edit acceptance rate: of the edits Claude proposed, how many you kept rather than rejected
- Languages & file types: lines changed per language, from the files Claude edited
Projects, branches and recent work
Projects ranks the folders you worked in, with the git branches the sessions started on under it. Recent work lists your last ten sessions with their title, project, surface, prompts and tool calls, and chips for what came out of each: an output, a commit, the cost.
Session length, modes and versions
Three smaller panels finish the picture. Session length shows how long sessions ran, with the median and the longest. Permission modes shows how hands-off you ran Claude Code: asking before edits, accepting edits, plan, auto or bypass. Claude Code versions shows which versions your sessions ran on, handy when something changed after an update.
Copy your recap
At the bottom, Period recap puts the range into five numbers. Copy recap copies a one-line summary with numbers only: no titles, projects or text. Share it if you want to; it is your choice.