Ccstory – Weekly recap of what you did in Claude Code
ccstory is a tool that generates a weekly recap of activities in Claude Code, summarizing time spent, costs, and work completed across categories like coding, writing, and research. It reads local session logs and produces a categorized report with optional AI-generated narratives for each session. Designed for users who want to track productivity or understand how their usage metrics from ccusage were accumulated.
- ▪ccstory analyzes local Claude Code session logs to generate time and cost recaps by category.
- ▪The tool categorizes work into buckets like coding, writing, and research based on project folder names or user-defined rules.
- ▪Users can generate reports for different time windows and enhance session summaries with LLM-generated narratives using the --llm-narrative flag.
- ▪A trend feature visualizes activity over time with sparklines, and cost metrics can be compared against a monthly quota.
- ▪Reports are saved in Markdown format and can be customized for output formats like Obsidian with wikilinks.
Opening excerpt (first ~120 words) tap to expand
ccstory Your Claude Code week, in plain English. Reads ~/.claude/projects/**/*.jsonl locally and writes a categorized recap with active hours, costs, and a per-bucket narrative. Sibling to ccusage: ccusage tells you how much you spent · ccstory tells you what on. Who this is for People who want to write a weekly status without scrolling scrollback. People who saw a ccusage number and want to know what kind of work those tokens went to. People who do a Sunday-night reflection on what they actually shipped. Quick start pipx install ccstory ccstory init ccstory week That's it. init is a one-time auto-categorize step that scans your recent sessions; ccstory week produces the recap. Full report saves to ~/.ccstory/reports/recap-*.md.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at GitHub.