whoburnedmore
<p> Spotify Wrapped for Claude, Codex & a Public leaderboard. </p> <p> <a href="https://www.producthunt.com/products/whoburnedmore?utm_campaign=producthunt-atom-posts-feed&utm_medium=rss-feed&utm_source=producthunt-atom-posts-feed">Discussion</a> | <a href="https://www.producthunt.com/r/p/1172842?app_id=339">Link</a> </p>
Last verified:
What is whoburnedmore?
whoburnedmore is a CLI and dashboard for ranking AI coding-agent usage by token burn, so you can see who burned more across a shared board. It reads local session or usage logs from tools like Claude, Codex, Cursor, and opencode, then aggregates totals into a leaderboard and cost view. The website emphasizes that only totals leave your machine in normal mode, not your code, which makes it aimed at privacy-conscious developers. It is also available in a local-only mode, so the dashboard can run privately on your own machine.
The product is built for people who use AI coding tools heavily and want a simple way to compare usage, costs, and streaks. It surfaces per-user totals, today’s burn, top tool, top model, and update timing, so it works as both a personal dashboard and a team leaderboard. The homepage also frames it as a playful, gamified way to track “burned” tokens rather than a formal billing system. That makes it useful for indie developers, teams, and anyone curious about how much AI-assisted coding they are actually consuming.
Its core appeal is that it combines data collection, ranking, and visualization in one lightweight command. The site shows a live-style board with medals, token totals, estimated cost, daily burn, and streak indicators, plus a summary of overall burned tokens and estimated spend. The local mode option suggests a privacy-first approach for users who do not want their code or raw logs uploaded. Overall, it is best described as a token-usage scoreboard for AI coding workflows.
Based on the homepage, it is especially suited to developers already using multiple AI coding assistants and wanting a quick, competitive snapshot of usage. It is less about deep analytics and more about giving an immediate answer to the question of who is burning the most tokens. The tone of the site is casual and leaderboard-driven, so it also appeals to teams that like light competition or internal visibility into AI usage.
The site does not present itself as a full developer platform or enterprise expense suite; it appears narrower and more opinionated. Its main value is transparency around token burn and cost, with a strong emphasis on local data handling. That makes it a niche but practical tool for AI-native developers who want visibility without a heavy setup.
whoburnedmore pricing
Pricing model: Freemium
The website itself presents a free, open command-based tool and highlights a local-only option with --local, but it does not show any paid plans, tiered pricing, or subscription details on the homepage. The homepage focuses on usage tracking, leaderboard display, and privacy rather than monetization. No paid features, limits, or add-ons are described on the site content available here.
whoburnedmore pros
- Tracks AI token burn across coding tools
- Shows a ranked leaderboard
- Displays total tokens burned
- Shows estimated cost
- Surfaces today’s burn amount
- Supports Claude usage tracking
- Supports Codex usage tracking
- Supports Cursor usage tracking
- Supports opencode usage tracking
- Reads local session/log files
- Keeps code on your machine in normal mode
- Offers a local-only mode
- Shows update timing on the board
- Displays streak indicators
- Shows top tool per user
- Shows top model per user
- Works as a CLI command
- Provides a dashboard view
- Useful for team-wide usage comparison
- Gamifies AI coding consumption
whoburnedmore cons
- Focused only on token burn tracking
- Not a full billing or expense platform
- Requires local logs or session files
- Depends on supported coding tools
- Leaderboard style may not fit all teams
- Appears optimized for AI coding workflows only
- No evidence of deep historical analytics
- No clear enterprise admin features on the homepage
- May be less useful for non-CLI users
Frequently asked questions about whoburnedmore
What does whoburnedmore track?
It tracks AI coding token burn and turns that usage into a leaderboard. The homepage shows totals, today’s burn, estimated cost, streaks, top tool, and top model for each entry.
How does it work?
It reads the usage or session logs that AI coding tools already write locally, sums the totals, and displays them on a dashboard. The site describes it as a one-command experience for ranking AI coding usage.
Which tools are supported?
The homepage explicitly shows support for tools such as Claude, Codex, Cursor, and opencode. The leaderboard entries also label users by their top tool, which suggests the tool is built around those coding-agent ecosystems.
Does it upload my code?
The site says only totals leave your machine in normal mode, not your code. It also offers a --local option for a dashboard that stays on your own machine.
What does the dashboard show?
The board shows ranked users, token totals, estimated cost, today’s burn, update timing, streaks, and which tool or model each person used most. It also shows overall totals such as total tokens burned and estimated cost burned so far.
Who is this for?
It is aimed at developers and teams using AI coding assistants who want visibility into usage and cost. The leaderboard format suggests it is also meant for people who enjoy comparing activity across a team or community.
Can I use it privately?
Yes. The homepage says you can add --local and open the dashboard on your own machine, with nothing leaving your computer.
Is it just a leaderboard?
No. While the leaderboard is the main visual, it also provides totals, costs, per-user tool breakdowns, and daily burn figures. That makes it more than a simple ranking page.
What kind of cost information does it show?
It displays an estimated cost alongside token totals, both per user and overall. The homepage treats this as a burn and spend tracker rather than a detailed invoicing tool.
Does it require setup with a cloud account?
The homepage does not describe any cloud account requirement. Instead, it emphasizes local log reading and a local-only mode, which suggests the workflow is designed to work from your existing local environment.