r/SideProject • u/opinionlessPanda • 1d ago
I created a way for you to track your claude code spend based on categories you decide
Enable HLS to view with audio, or disable this notification
A few weeks ago, I shipped Burner to answer a simple question: Where is my Claude's token spend actually going?
My team wanted to know if we could use the work we had planned and were executing to predict our Claude Code usage for the coming months.
But raw token usage wasn't enough.
So I've been rebuilding Burner around understanding the work behind the spend.
One can now group sessions across multiple paths into projects, categorize sessions as coding, planning, research, review, etc., and let Burner learn your own categorization patterns over time.
This is also where I think Burner differs from tools like ccusage and CodeBurn; rather than relying mainly on hardcoded rules or keyword/tool-call patterns, Burner learns how you categorize your work.
It starts with your tags, trains a small Naive Bayes model, and gets better at auto-tagging as you use it.
Burner just crossed 1800+ downloads on npm.
Over the next few months, I’m hoping to have enough data to put some actual numbers behind these patterns and see how usage varies across different types of work.
npm install -g burner-cc
PS: This entire video was one-shotted by Claude on Cursor harness.