Claude Code insights and usage: what your sessions say about you

Claude Code writes each session to a file on your computer, under ~/.claude/projects/. Every tool on this page reads those files. By default Claude Code deletes transcripts after 30 days, so each tool sees about a month of your work unless you raise the cleanupPeriodDays setting (Claude Code settings).

Sessions from other computers and from claude.ai are not included in Claude Code’s own numbers (Claude Code docs). So the first question is what you want to know: what you spent, how close you are to a limit, how you work, or who made the calls.

/insights is built into Claude Code. Anthropic describes it as "a report on how you work rather than how many tokens you’ve used": an HTML report on what you work on, friction points such as misunderstood requests or buggy code, and suggestions for using Claude Code more effectively (Claude Code docs). The latest report is saved to ~/.claude/usage-data/report.html, with a dated copy of each run.

Two things to know before you run it. A single run analyzes up to 200 sessions it has not seen before and skips very short ones. And the analysis runs through your normal account, so its tokens count against your plan or API usage (Claude Code docs).

People who run it often find it humbling. One developer "expected a pat on the back" and "got a diagnosis instead" (r/ClaudeAI). Another "learned more about my own mistakes than about the tool" (r/ClaudeCode).

Its suggestions are about using Claude Code better: features to try, and fixes to your setup. It is a snapshot of recent sessions, not a record of how you change over months.

/usage (also /cost and /stats) is built into Claude Code. It shows session cost, plan usage limits and activity stats (Claude Code commands). The figures are approximate and computed from local session history on this machine (Claude Code docs).

ccusage is a free, open source command line tool (MIT licence, about 19,400 GitHub stars on 8 November 2026). Run npx ccusage@latest and it prints daily, weekly, monthly and session reports of tokens and estimated cost, including Claude’s 5-hour billing windows (ccusage). It only reads files on your computer and says "your usage data never leaves your computer". Besides Claude Code it reads Codex, Gemini CLI, Antigravity, GitHub Copilot CLI and many other agents (ccusage guide). Its costs are estimates, not your bill.

People mostly use these for money and limits. The best loved ccusage post on r/ClaudeCode is someone printing a paper receipt after every session (r/ClaudeCode).

Claude Code Usage Monitor is a free, open source terminal app (MIT licence, about 8,800 GitHub stars on 8 November 2026). Install it with uv tool install claude-monitor and run claude-monitor. It shows a live view of your current session and burn rate, daily and monthly tables of tokens and cost, and a forecast of when your session will run out (Claude Code Usage Monitor).

It is the tool for one question: will I hit my limit before I finish? It covers Claude Code only. It launched on Hacker News and reached 245 points the same day (Show HN).

We made this one. Your agent asks before it runs things, but most of the time something else answers for you: a rule you saved weeks ago, the permission mode, auto mode or a hook. who-said-yes counts how many of your agent’s actions you approved yourself, at the prompt, in that moment. It asks you to guess first (who-said-yes).

Run npx github:skprasad-korture/who-said-yes. It reads the Claude Code and Codex logs on your computer, has no network code, and needs no account or email. It is free and open source (MIT). Codex logs its approval rule for each turn, not each answer you give, so for Codex it shows how many actions ran under "never ask" rather than your own yeses.

What it found for one of us: on 8 November 2026, the last 30 days of SK’s Claude Code logs held 16,813 agent actions across 96 sessions. He said yes himself 35 times, about 1 in every 480 actions. 732 of his 738 file edits ran with no prompt shown to him.

Every tool above counts what happened: tokens, cost, limits, approvals, sessions that went wrong. None of them tells you whether you are still good at the work as agents do more of it.

How fast it feels is a poor guide. In METR’s 2025 study, experienced open source developers expected AI to make them 24% faster, and afterwards believed it had made them 20% faster. Measured, they took 19% longer (METR).

Some questions only your own sessions can answer. Did you make your call before you asked, or after the agent offered one? When a run went wrong, did you stop it, or let it keep going? How long did the agent work with no message from you?

How KORTURE.ai measures this: Sense reads your own chats on your computer, gives each stretch of work a number, and shows the moments behind it in your own words. Every line it shows is checked against what you actually wrote (what Sense is).

• Run /insights once and read the friction part. For each item, ask whether it was the agent’s mistake or your call.
• Run npx ccusage@latest daily and set your heaviest days next to the days you shipped what you meant to.
• Run who-said-yes and make your guess first. The gap between your guess and the count is the interesting number.