isas1/claude-model-compare — explained in plain English
Analysis updated 2026-05-18
See which Claude model you use most for different kinds of coding tasks.
Compare session length, tool usage, and autonomy between Claude models.
Export your own usage statistics as JSON or CSV for further analysis.
Check how much work gets delegated to subagents versus the main conversation.
| isas1/claude-model-compare | 0xallam/my-recipe | 0xhassaan/nn-from-scratch | |
|---|---|---|---|
| Stars | 0 | — | 0 |
| Language | Python | Python | Python |
| Last pushed | — | 2022-11-22 | — |
| Maintenance | — | Dormant | — |
| Setup difficulty | easy | moderate | moderate |
| Complexity | 1/5 | 2/5 | 4/5 |
| Audience | developer | general | developer |
Figures from each repo's GitHub metadata at analysis time.
No pip installs needed, just Python 3.8+ standard library and a browser.
This project is a local dashboard that shows how you personally use different Claude AI models inside Claude Code, the coding assistant tool. It works by reading transcript files that already exist on your own computer from past coding sessions, and turning them into charts and tables you can browse in a web browser. The idea is to answer questions you might have about your own habits, such as whether you use a more powerful model like Opus for different kinds of tasks than a lighter model like Sonnet, or whether one model tends to run longer sessions, call more tools, or hand off more work to helper agents. The dashboard shows things like session counts, how many messages and tool calls happen per turn, which tools each model uses most, and how work is spread across different categories over time. You can also download the underlying numbers as JSON or CSV files. Privacy is treated as a core design choice rather than just a promise. The tool only reads your transcripts, never writes to them, and only extracts numbers such as token counts, message counts, and timings. It never touches your actual prompts, responses, or code. Everything runs locally in your browser with no analytics and no network calls, and the generated data file is excluded from being uploaded if you were to share your own copy of the project. Getting started just requires Python 3.8 or newer, with no extra packages to install. You clone the repository, run one script to scan your Claude Code transcripts and build a data file, then run a second command to start a simple local web server and view the dashboard in your browser. The author is upfront that the dashboard describes patterns rather than judging model quality: differences between models mostly reflect which model you happened to choose for which task, not which model is better. There are 64 automated tests using fake, synthetic transcript data to check the tool's logic. The project is released under the MIT license, a permissive license that allows free use and modification, including commercially, as long as the copyright notice is kept.
A local dashboard that mines your own Claude Code transcripts to show how you actually use different Claude models, with nothing uploaded.
Mainly Python. The stack also includes Python, HTML, JavaScript.
Use freely for any purpose, including commercial use, as long as you keep the copyright notice.
Setup difficulty is rated easy, with roughly 5min to a first successful run.
Mainly developer.
This repo across BitVibe Labs
Verify against the repo before relying on details.