daaain / daaain/claude-code-log

Showcase: claude-code-conversation-analyzer — analytics dashboard built on top of claude-code-log

Open
#130 3 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

documentation
Dominant language
Python
Stars
1.2k
Forks
98
Avg merge
3d 2h
Merged PRs (30d)
13

Description

Hi @daaain — first off, huge thanks for claude-code-log. The SQLite cache it produces (claude-code-log-cache.db) turned out to be the perfect substrate for a project I've been building, and I wanted to share it here in case it's interesting to you or other users of this tool.

What I built

claude-code-conversation-analyzer — a dashboard that reads the cclog SQLite DB and layers on:

  • Cost analysis — per-session and per-model cost breakdowns using current Anthropic pricing (input/output/cache-creation/cache-read tokens)
  • Quality scoring — weighted scoring across cache usage, conversation length, query specificity, context utilization, and prompt efficiency, with letter grades (A–F)
  • Compaction detection — flags cache drops >10k tokens as compaction events
  • Better UI — Next.js 16 + React 19 dashboard with:
    • Project overview grid with grade distribution
    • Conversation list with sortable metrics
    • Expandable conversation cards with token charts (Recharts) and message transcripts
    • Full-text search across projects and sessions
    • Dark/light theme

How it integrates with claude-code-log

The pipeline runs claude-code-log as the data-generation step, then augments the resulting SQLite DB with two extra tables (session_costs, session_quality). Nothing in the cclog DB itself is modified — the analyzer is purely additive. A make all target handles the full flow: clone/update cclog fork → regenerate transcripts → run analysis → serve dashboard.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

This is a showcase rather than a requested code change. Review the linked claude-code-conversation-analyzer project and its make all pipeline, then determine whether the repository has a documented place for external integrations; done would be a clear, agreed presentation of the project's cclog and SQLite relationship.

Written by the indexing model from the issue text.

Assessment

Tech stack
next.js, python, react, sqlite
Domain
cli, content, databases, documentation, web-dev
Issue type
Documentation
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.