<aside> ℹ️
Difficulty: Intermediate • Time: 15 minutes • Tools: Claude Code
</aside>
After a few weeks with an AI coding assistant, you develop habits. Some are good — you learn which prompts get better results, which tasks to delegate, when to step in. Others are invisible. You repeat the same instructions every session, reach for tools that waste context, and let the AI make decisions you should be making yourself.
The problem is you can't see any of this while you're in the flow. You'd need someone watching over your shoulder across dozens of sessions, spotting the patterns you can't.
Claude Code has a built-in command that does exactly that. By the end of this guide, you'll have a personalised report showing how you actually use AI — not how you think you use it — and specific changes to make your workflow better.
Open Claude Code in any project directory and type:
/insights
That's it. No flags, no configuration.
The command reads your session transcripts from the past 30 days — up to 50 sessions — and generates an interactive HTML report. It opens automatically in your browser when it's done.
The analysis takes a minute or two. Longer if you've been busy. It's processing every conversation you've had with Claude Code: the tools you called, the instructions you gave, the friction points, the wins.
Your report lands in ~/.claude/usage-data/report.html. You can reopen it anytime.
The report has four sections, each built from your actual session data. No generic advice — everything it surfaces comes from what you specifically did.
Cards for each project you've worked on, showing session counts, tools used, and languages touched. This is the overview: where you're spending your time and what kind of work you're asking Claude to do.
If you see a project with 15 sessions that are all short, that's a signal. Either the work is genuinely quick, or you're context-switching too often and burning tokens on ramp-up.