Command reference ยท Claude Code
/insights
Generates a report that analyzes your own Claude Code sessions, including project areas, interaction patterns, and friction points.
The /insights command generates a report analyzing your own Claude Code sessions โ such as which parts of the project were worked on most, what interaction patterns occur, and where friction points arose. The report is generated as a file, whose location is linked in the response, for example to show which repositories received the most time or whether certain requests repeatedly led to follow-up questions. Unlike the organization-wide analytics dashboards for Team and Enterprise plans, which show adoption, spending, and contribution metrics across multiple users, /insights only analyzes your own local session history โ without logging into claude.ai/analytics and without GitHub integration. The command is therefore better suited to personal reflection on your own workflow than to team reporting or cost control. It doesn't provide an instant short summary of the current session; that's what /recap is for.
โ WHEN TO USE IT?
Reflecting on your own Claude Code usage after an intense project phase
Run /insights after a work week to see which parts of the project received the most work
Spotting recurring friction points in your own workflow across multiple sessions
Use /insights to surface patterns like frequent follow-up questions or misunderstandings
โ WHEN NOT TO?
Evaluating team-wide usage, cost, or contribution metrics
/insights only analyzes your own local session history, not other users' data
Better: Use the analytics dashboard at claude.ai/analytics/claude-code (Team/Enterprise) or platform.claude.com/claude-code (API)
An instant one-sentence summary of the running session
/insights analyzes sessions retrospectively for patterns, but doesn't provide a quick status
Better: Use /recap for a one-line summary of the current session
SOURCES
- Claude Code docs (official) โ code.claude.com
MORE COMMANDS ยท Claude Code