Read Claude Code billing logs
Reads logs that Claude Code already records for billed tokens.
Coding / product dossier
claudebill
Reads Claude Code logs to show costs by session, project, branch, model, and day.
Product brief
What claudebill does.
Claude Code already logs every token it bills. claudebill reads those logs and shows cost per session, project, git branch, model, and day, plus what prompt caching saved you. Retroactive, offline, zero dependencies. npx claudebill.
Why we selected it
A narrow but valuable open-source utility for teams scaling Claude Code use: it reads existing local logs to expose cost by session, project, branch, model, and day without dependencies.
- Best for
- AI Developer FinOps
- Category
- Coding
- Daily picks
- 1
- First selected
- 2026-09-20
Product preview saved with our daily selection
Capability scan
What it can help with.
Only capabilities supported by the product information we collected are listed here.
Show cost by session and project
Reports cost per session and per project.
Break down cost by branch, model, and day
Shows cost by git branch, model, and day.
Report prompt-cache savings
Shows what prompt caching saved.
Analyze historical logs offline
Is described as retroactive, offline, and having zero dependencies.
Best-fit use cases
Review the cost of individual Claude Code sessions.
Compare Claude Code costs across projects or git branches.
Examine cost by model or day.
Identify reported savings from prompt caching using existing logs.
FAQ
Before you open it.
What data does claudebill use?
It reads the token billing logs that Claude Code already records.
How can costs be broken down?
Costs can be viewed by session, project, git branch, model, and day.
Does it show prompt-cache savings?
Yes. The listing says it shows what prompt caching saved.
Can it analyze past usage?
Yes. It is described as retroactive.
Are dependencies required?
The listing states that claudebill has zero dependencies.