I built a tool that reads your Claude Code session transcripts and tells you how much time you actually spend with AI.
My results: 3,479 sessions. 116 hours. 50 days tracked, 47 active. The tool's response: "Rest days exist for a reason."
Why This Exists
I pay $200/month for Claude Code. I run it autonomously on WSL2. I knew I was using it a lot. I didn't know how much.
There's no built-in way to see your usage patterns. Claude Code logs everything to ~/.claude/projects/ as JSONL transcript files, but nobody reads those. They just accumulate.
So I built a CLI that reads the timestamps and gives you a reality check.
The Tool
npx cc-session-stats
Zero dependencies. Reads only the first and last line of each transcript file. No data leaves your machine.
It shows:
- Total sessions and hours
- Average session duration
- Longest single session
- Hours by day of week
- Active hours heatmap
- Per-project breakdown
- Consecutive day streak
- Health warnings when patterns look concerning
My Results
? Overview
Sessions: 3479
Total hours: 115.9h
Active days: 47 / 50 days
Avg per day: 2.5h
? Longest Session
8.5h on 2026-02-28 - cc-loop
? Hours by Day of Week
Sun ??????????????? 20.3h
Fri ??????????????? 20.5h
Thu ??????????????? 19.7h
? Streak
Longest consecutive days: 35
? Health Warnings
? 35 consecutive days of AI usage. Rest days exist for a reason.
47 active days out of 50 since I started. Three days off in seven weeks. My longest consecutive run: 35 days straight. Not great.
The day-of-week breakdown is interesting: Sunday and Friday are my highest-usage days. Weekends aren't rest days when you have an autonomous AI agent running.
The Health Angle Nobody Talks About
Since I started using Claude Code daily:
- I threw out my back (????? - a Japanese term for acute lower back pain)
- My shoulder tension doubled
- My hairdresser told me "the area above your forehead is incredibly tense" from screen time
- I had a two-week brain meltdown from forced multitasking
AI productivity tools are marketed as time-savers. Nobody mentions that they also increase your sitting time, your screen time, and your cognitive load.
The tool doesn't fix this. But seeing the number - "50 consecutive days" - makes it real in a way that vague awareness doesn't.
What The Tool Flags
| Pattern | Warning |
|---|---|
| Sessions over 3 hours | Your spine has opinions |
| 7+ consecutive days | Rest days exist for a reason |
| Average session > 2 hours | 90-minute focus blocks are backed by research |
| 6+ hours/day average | That's a full workday of sitting |
The last tip is always the same: "Stretch your hip flexors. They're angry. Trust me."
The cc-toolkit
| Tool | Question |
|---|---|
| cc-health-check | Is your AI setup safe? |
| cc-session-stats | How much are you using AI? |
| cc-audit-log | What did your AI do? |
| cc-cost-check | How much is your AI costing you? |
| cc-wrapped | Spotify Wrapped, but for Claude Code |
| cc-roast | Your CLAUDE.md, brutally honest |
Want to see your stats in a visual format? Open CC Wrapped in your browser and select your ~/.claude folder directly - no npm needed. Or run npx cc-session-stats --json and paste the output for the same result.
Not sure how you compare? Claude Code Bingo - 50 "it happened to me" moments.
106 tools total: cc-toolkit ?
Try It
# Run instantly with npx (no install needed)
npx cc-session-stats
GitHub: github.com/yurukusa/cc-session-stats
What's your streak?
I run Claude Code 24/7 on WSL2 and document everything that happens - including the physical damage. This is the tool I built because seeing "50 days" was the wake-up call I needed.
More tools: Dev Toolkit - 56 free browser-based tools for developers. JSON, regex, colors, CSS, SQL, and more. All single HTML files, no signup.
Top comments (0)