Claude Code deletes its session transcripts after 30 days by default, no message, so any usage tool reading that folder only ever sees the last month. I wanted to compare months and see what switching model actually did to cost, so claudit ingests from a bucket you keep instead (Cloudflare R2, or a local dir as file://). mine goes back to January. the bucket holds the raw transcripts, tool output included, so keep it private it reads Claude Code session JSONLs, Codex rollouts and both Kimi CLI formats. on the page: cost by model with the 5m vs 1h cache write split (1.25x vs 2x input price), token breakdown, reply latency, tool error rate, activity heatmap, context growth per session. costs are API list price equivalents, not what a sub bills you. it doesn't grade sessions, the reading is yours feedback I'd actually use: a number that looks wrong to you, with the arithmetic a stat you'd want that isn't there a harness it doesn't read yet, ideally with a real transcript (sanitized is fine) FastAPI, Postgres, React with in-browser Babel, no build step. docker compose up boots it on sample data, no .env, no outbound calls. MIT, panels ported from nhz-io/ccusage-plot live one, guest login is read-only: https://all.nitjsefni.eu https://github.com/Nitjsefnie/claudit   submitted by   /u/Nitjsefnie [link]   [comments]