I like this a lot An interesting next iteration would be to add a functionality that evaluates a user's work for inefficiencies and suggests where they can improve cut cost. Might be outside the scope of your project, but it could be interesting.
Show HN: CodeBurn – Analyze Claude Code token usage by task
11–20 of 37 posts
Re: Show HN: CodeBurn – Analyze Claude Code token usage by task
#12"Built this after realizing I was spending ~$1400/week on Claude Code with almost no visibility into what was actually consuming tokens." holy slop. the $200/month plan has NEVER hit rate limits for me and I often run 5+ tabs of concurrent agents in a large 300k LoC codebase
not $1,400 out of pocket, thats the API equivalent cost of the tokens. I am on the $200/month Max plan :D.
In my case I mostly consume every bit of the weekly subscription.
Re: Show HN: CodeBurn – Analyze Claude Code token usage by task
#13I like this a lot An interesting next iteration would be to add a functionality that evaluates a user's work for inefficiencies and suggests where they can improve cut cost. Might be outside the scope of your project, but it could be interesting.
already on that probably in an hour it will be published. will let you know once it does.
Re: Show HN: CodeBurn – Analyze Claude Code token usage by task
#14[flagged]
Re: Show HN: CodeBurn – Analyze Claude Code token usage by task
#15"Built this after realizing I was spending ~$1400/week on Claude Code with almost no visibility into what was actually consuming tokens." holy slop. the $200/month plan has NEVER hit rate limits for me and I often run 5+ tabs of concurrent agents in a large 300k LoC codebase
The $200/month plan throttles you when you hit limits - you just wait in a queue. API usage at $1400/week means unthrottled, parallel execution with no waiting. These are very different use cases, and for teams or heavy automation workflows the API cost can make sense if the time savings justify it.
Re: Show HN: CodeBurn – Analyze Claude Code token usage by task
#16I like this a lot An interesting next iteration would be to add a functionality that evaluates a user's work for inefficiencies and suggests where they can improve cut cost. Might be outside the scope of your project, but it could be interesting.
already on that probably in an hour it will be published. will let you know once it does.
Awesome!
Re: Show HN: CodeBurn – Analyze Claude Code token usage by task
#17> The interface is an interactive terminal UI built with Ink (React for terminals) Just like Claude Code btw. I'm working on a custom harness because I don't like or trust some of the ones out there, so I'm going to build one purely for myself and my own needs to see just how they work, and figure out some of what you've learned by looking at how Claude works, so I might add your project to my list of tooling to look…
yeah Ink, it was the fastest path to something that felt native next to Claude Code itself
React is very good at what it does.
Re: Show HN: CodeBurn – Analyze Claude Code token usage by task
#18Re: Show HN: CodeBurn – Analyze Claude Code token usage by task
#19This is cool.
I do find the activities a little suspect - it has 1 turn of planning for me in the last 30 days. I have claude write plans first before every coding session, often using one agent session to plan and then output a plan file, and then others to execute on it. I also have several repos dedicated to 'planning' in the sense of what should I do next based on what emails/tickets/bugs etc. I have. In other words - I do all kinds of planning!
Re: Show HN: CodeBurn – Analyze Claude Code token usage by task
#20[dead]