git404hub

what is ccstory fr?

atomchung/ccstory — explained in plain English

Analysis updated 2026-05-18

21PythonAudience · developerComplexity · 2/5Setup · easy

tl;dr

A command-line tool that reads your local Claude Code session logs and turns them into a readable weekly report of what you actually worked on.

vibe map

mindmap
  root((ccstory))
    What it does
      Reads Claude Code logs
      Categorizes sessions
      Writes narrative reports
    Tech stack
      Python
      Claude Code logs
      pipx
    Use cases
      Weekly retrospectives
      Usage breakdowns
      Obsidian export
    Audience
      Claude Code users

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

what do people make with this?

VIBE 1

Generate a weekly Markdown report of how your Claude Code time was spent.

VIBE 2

See a category breakdown of coding, writing, and research activity from your sessions.

VIBE 3

Get an AI-written narrative summary of what you shipped each week.

VIBE 4

Export your usage report to Obsidian for personal knowledge tracking.

what's the stack?

Pythonpipx

how it stacks up fr

atomchung/ccstory0whitedev/detranspiler2951461586/mulerun-pool
Stars212121
LanguagePythonPythonPython
Setup difficultyeasyhardmoderate
Complexity2/54/53/5
Audiencedeveloperdeveloperdeveloper

Figures from each repo's GitHub metadata at analysis time.

how do i run it?

Difficulty · easy time til it works · 5min

Runs entirely on local Claude Code session logs, optional narrative mode uses your existing Claude Code session.

in plain english

ccstory is a command-line tool for people who use Claude Code, Anthropic's AI coding assistant, and want a human-readable summary of how they've been spending their time with it. Where ccusage (a companion tool) tells you what your Claude API bill was, ccstory reads the same local log files and tells you what the tokens actually went toward: coding, writing, research, or whatever categories you define. It reads Claude Code's session logs stored in ~/.claude/projects/ on your machine, groups the sessions into time buckets and activity categories based on folder name rules or by having Claude analyze the content of each session, and produces a formatted report showing active hours, number of sessions, token output, cost, and a breakdown of time spent per category. An optional narrative mode calls Claude locally to write 2-3 sentence summaries per category and one-liner descriptions per session, turning the numbers into a written account of what you actually shipped that week. The full report is saved as a Markdown file, an Obsidian export option adds YAML frontmatter for use in personal knowledge management vaults. You would use this for weekly retrospectives, status updates, or just to understand where your AI usage is going after you see a surprising bill. Everything runs locally, no telemetry, no external service, and the optional AI narrative feature uses your existing Claude Code session rather than a separate API key. The tech stack is Python 3.10 or later, installed as a package via pipx. The full README is longer than what was provided.

prompts (copy fr)

prompt 1
Install ccstory with pipx and generate a report from my ~/.claude/projects/ session logs.
prompt 2
Run ccstory's narrative mode and explain the categories it found in my Claude Code usage.
prompt 3
Show me how to export a ccstory report with Obsidian-compatible frontmatter.
prompt 4
Help me define custom activity categories for ccstory to classify my coding sessions.

Frequently asked questions

what is ccstory fr?

A command-line tool that reads your local Claude Code session logs and turns them into a readable weekly report of what you actually worked on.

What language is ccstory written in?

Mainly Python. The stack also includes Python, pipx.

How hard is ccstory to set up?

Setup difficulty is rated easy, with roughly 5min to a first successful run.

Who is ccstory for?

Mainly developer.

peek the repo → explain another one

This repo across BitVibe Labs

double-check against the repo, no cap.