Skip to content
Lesson 1 of 714% of the course

See your Claude Code usage in five minutes

Open your ~/.claude/projects folder in Usage Insights for Claude Code and get a dashboard of your Claude Code history, read in your browser and never uploaded.

Nothing loads from YouTube until you press play. Then Google receives your IP address and may set its own storage. Narrated with an AI-generated voice. Privacy

Claude Code writes every session to a file on your computer: each prompt, each response with its token counts, each tool call and whether it worked. Usage Insights for Claude Code turns those files into a dashboard. This lesson gets you from nothing to your first numbers.

Drop the folder, pick it, or start with the sample team.

Find your history

Claude Code keeps one folder per project and one .jsonl file per session:

SystemFolder
macOS and Linux~/.claude/projects
Windows%USERPROFILE%\.claude\projects

The .claude folder is hidden. In a file picker, press ⌘ ⇧ . on a Mac or Ctrl H on Linux to show hidden folders. On Windows, type %USERPROFILE%\.claude into the picker's address bar.

Open it in the browser

Open Usage Insights for Claude Code and either drag the projects folder onto the page or press Choose the folder and pick it. A bar shows how much has been read. A folder of several gigabytes takes about half a minute, because the files are read line by line in the background of your tab.

Nothing is uploaded. The page has no server to send your files to: it opens them the way a text editor would, keeps counts, names and times, and drops the text of your prompts and Claude's answers as it reads.

Or try the sample first

Not ready to open your own history? Try the sample loads a made-up team of 26 people over 120 days, so every view has something to show, the Team view too. The chip at the top says Sample team (illustrative) while it is loaded.

Read the first row

The Me view opens first. Its top row is the short answer to "what did I do with Claude?":

Six numbers for the range you chose, then prompts per day.
  • Active days: days with at least one prompt, and how many of the working days that is
  • Conversations / sessions and Prompts sent, with prompts per session and per day
  • Active time: an estimate from the gaps between events, next to the time Claude spent working
  • Streak: days in a row with activity; a weekend without it does not break the run
  • Tokens & cost: what the sessions cost, from Claude Code's own record

Pick a range and a project

Above the numbers, choose 7 d, 30 d, 90 d, 12 m or All, and pick a project to see only its sessions. Point at any chart for its numbers, and at any label for how that number is worked out.

The next lesson reads the rest of the Me view: when you work, what you built and what you used to build it.

Your progress stays in this browser only.
Contact