claudebill
Product Hunt Fakhar ul Hassan
Claude Code already logs what it bills. claudebill turns that into session-by-session cost breakdowns.
Based on reporting by Product Hunt, Fakhar ul Hassan — read the original for the full story.
Summary, retelling and take written by AI under human oversight; images are AI-generated illustrations. How we work · Report an error
Claude Code already keeps the token logs. claudebill takes those logs and turns them into something easier to read: cost per session, project, git branch, model, and day.
It also shows what prompt caching saved along the way. That matters because the bill is often hidden in the mess of day-to-day coding, not in one tidy total at the end.
The tool is retroactive, so it can look back at existing logs instead of waiting for new ones. It works offline, and it ships with zero dependencies.
If you want to try it, the command is simple: npx claudebill. That’s a very small wrapper around a very specific pain point, which is often exactly the right size for a good developer tool.
My take — AI-written commentary, not fact-checked reporting
This is the kind of brutally practical tooling the AI world needs more of and less parade music. The hype machine loves agentic everything; the bills do not. Open source, narrow, and a little unglamorous usually beats another glossy demo with a bigger promise and a shorter half-life.
Read more about this at: Product Hunt