Claude Insights Motion Study
00.0s / 26.0s
Claude Code /insights

Type once.
Your last 30 days answer back.

Start with a terminal command, then watch the report resolve into what helps you code better next time.

sessions
changes
git activity
friction
# generate local coding report
$
A typing-led opening cue. The terminal is the entry point, not a decorative flourish.
local analysis ready
Insights report

One clear picture of your coding flow.

30 daysRecent sessions compressed into one report.
PatternsRepeated habits and recurring friction surfaced.
RulesSuggestions transformed into reusable guidance.
Next stepsMonthly checkpoints for steady workflow improvement.
workflow signal 36 files change surface
git activity
report ready
On-screen text only 01 / 04
Workflow analysis

Analyzes your real workflow.

Not a vague summary. It watches for recurring session patterns, changes, and where time or clarity gets lost.

sessions
changes
patterns
30-day activity line
Snapshot
241Ktokens across recent coding sessions
36files touched over repeated iterations
18hsession time clustered into active blocks
11git moves connected to delivery flow
Patterns detected
Repeated prompt cleanup
Same instruction restated across sessions.
Late review loops
Corrections arrive after larger edits land.
Small wins
Clear specs accelerate the next session.
Flat motion / measured pacing 02 / 04
Privacy

Runs fully locally.

The analysis happens on your machine, so your code and session history stay where they already live.

local
private
no external server
Local report engine
Your report stays inside the workspace.
No logos / no stock visuals 03 / 04
Coaching output

Patterns become coaching.

The useful part is not the audit. It is what the audit turns into next time you open the terminal.

01
Generate ready-to-paste `CLAUDE.md` rules Turn repeated instructions into default behavior for the next session.
02
Spot recurring friction Find where prompts drift, edits miss, or review arrives too late.
CLAUDE.md
Before editing, summarize the task and inspect the existing file structure first.
Keep outputs concise and prefer flat motion for explainer assets.
Run /insights once a month.
personal coding coach
Your personal
coding coach.
Monthly checkpoint 04 / 04