Votre facture IA,
Détaillée
Outils pris en charge, 36 et ça continue
L'app de la barre de menus
Avant, vous le découvriez en fin de mois. Maintenant le chiffre reste à côté de votre horloge toute la journée, au-dessus de chaque fenêtre, et un clic ouvre la facture entière.
La dépense du jour se tient à côté de votre horloge. Aucun tableau de bord à ouvrir, aucun onglet à retrouver.
Consommation du forfait mesurée en direct pour chaque agent, avec le temps restant sur chaque fenêtre.
Totaux par agent d'aujourd'hui à toujours, en local ou combinés entre vos machines.
Dépenses ventilées par activité : code, débogage, développement, avec tours et taux de réussite du premier coup.
Swift natif. Lit uniquement les fichiers de session locaux. Rien ne quitte votre Mac. Sous Linux, le même chiffre vit dans votre barre GNOME.
L'app de bureau
La facture cesse d'être un chiffre et devient une carte : quel modèle, quel projet, quelle session, et si le travail payé a survécu.
Le flux de coût montre quel modèle a dépensé dans quel dépôt, sur la période de votre choix.
Un score d'efficacité bâti sur la réussite du premier coup, les hits de cache et la taxe des reprises.
Un total mensuel projeté, avec votre rythme comparé au mois dernier.
Dépenses attribuées aux branches et aux PR que le travail a réellement produits.
Gratuit et open source. macOS, Windows et Linux.
Le terminal
Lancez npx codeburn et tout le tableau s'ouvre là où vous êtes déjà. Sans installation, sans compte, sans configuration.
Basculez toute la vue entre aujourd'hui, une semaine, un mois, six mois ou tout ce que vous avez jamais lancé.
Projet, modèle, activité, outils, commandes shell, skills et agents, tout à la fois.
Taux de cache, tours et pourcentage de réussite du premier coup à côté de chaque coût, pas dans un rapport séparé.
Utilisations et coût des serveurs MCP, skills et agents délégués mobilisés par vos exécutions.
Aussi sur Homebrew. Les mêmes totaux que lisent la barre de menus et l'app.
De GitHub à Hacker News, les développeurs parlent de CodeBurn.
THIS TOOL SHOWS YOU EXACTLY WHERE YOUR CLAUDE CODE TOKENS ARE GOING. This guy was spending $200+ a day on Claude Code with zero visibility into what was eating the tokens. So he built a terminal dashboard that reads your session transcripts and classifies every single turn.
“This is actually pretty useful. Most people have no idea how much they're spending on AI tools until it adds up, so having it visible in the menubar makes a lot of sense. Really solid idea though, especially being open source.”
“Wait this is so sick! Definitely adding this when I get home”
“big thanks! needed this so badly.”
“Thank you - very interesting. I will try it out.”
“Beautiful”
“We definitely need to install this before our Polymarket scripts bankrupt us on API calls”
“CodeBurn Is The Latest Usage Tracker Blowing up On Github. 435 likes, 16K+ views.”
“You may want to bookmark this!! Do you know the true dollar cost of every Claude Code session?”
“Thanks for the quick turnaround and for getting the invariants right. The reconciliation guarantee is what makes this safe to consume.”
THIS TOOL SHOWS YOU EXACTLY WHERE YOUR CLAUDE CODE TOKENS ARE GOING. This guy was spending $200+ a day on Claude Code with zero visibility into what was eating the tokens. So he built a terminal dashboard that reads your session transcripts and classifies every single turn.
“This is actually pretty useful. Most people have no idea how much they're spending on AI tools until it adds up, so having it visible in the menubar makes a lot of sense. Really solid idea though, especially being open source.”
“Wait this is so sick! Definitely adding this when I get home”
“big thanks! needed this so badly.”
“Thank you - very interesting. I will try it out.”
“Beautiful”
“We definitely need to install this before our Polymarket scripts bankrupt us on API calls”
“CodeBurn Is The Latest Usage Tracker Blowing up On Github. 435 likes, 16K+ views.”
“You may want to bookmark this!! Do you know the true dollar cost of every Claude Code session?”
“Thanks for the quick turnaround and for getting the invariants right. The reconciliation guarantee is what makes this safe to consume.”
A handy little tool I discovered, specifically designed to keep tabs on the token bills for Claude Code and Codex. When you usually use AI to write code, where the tokens are spent, which model burns through money the fastest.
“Very nice. Feels like one of those tools that becomes obvious the moment you see your spend broken down this clearly. Looks like the project has great velocity now.”
“I'd love something like this Claude Desktop. Looks great.”
“Been using this a lot since I discovered it a few weeks ago. Thanks for building and sharing!”
“Looks like it may be useful, thank you”
“Looks cool! Is it able to track stats for models that I use through a non-opencode subscription? Like if I use gpt-5.3-codex through a chatgpt subscription in opencode, will I be able to see some usage stats for it?”
“This is a game changer for anyone trying to scale their agentic workflows without going broke. Visualizing where the tokens actually go makes it much easier to optimize your development budget.”
“CodeBurn, an open-source dashboard built by the AgentSeal team that answers the one question every developer using Claude Code or Cursor is frustrated about: where the hell did all my tokens go?”
“ah nice, you are doing some amazing work. Just to let you know — Visa has forked CodeBurn internally and suggested employees try it.”
“Thanks for shipping this so quickly. Two choices are nicer than what I proposed. NSStatusItem.variableLength is a cleaner answer, and Int((cost * rate).rounded()) rounds correctly where my version would silently truncate.”
A handy little tool I discovered, specifically designed to keep tabs on the token bills for Claude Code and Codex. When you usually use AI to write code, where the tokens are spent, which model burns through money the fastest.
“Very nice. Feels like one of those tools that becomes obvious the moment you see your spend broken down this clearly. Looks like the project has great velocity now.”
“I'd love something like this Claude Desktop. Looks great.”
“Been using this a lot since I discovered it a few weeks ago. Thanks for building and sharing!”
“Looks like it may be useful, thank you”
“Looks cool! Is it able to track stats for models that I use through a non-opencode subscription? Like if I use gpt-5.3-codex through a chatgpt subscription in opencode, will I be able to see some usage stats for it?”
“This is a game changer for anyone trying to scale their agentic workflows without going broke. Visualizing where the tokens actually go makes it much easier to optimize your development budget.”
“CodeBurn, an open-source dashboard built by the AgentSeal team that answers the one question every developer using Claude Code or Cursor is frustrated about: where the hell did all my tokens go?”
“ah nice, you are doing some amazing work. Just to let you know — Visa has forked CodeBurn internally and suggested employees try it.”
“Thanks for shipping this so quickly. Two choices are nicer than what I proposed. NSStatusItem.variableLength is a cleaner answer, and Int((cost * rate).rounded()) rounds correctly where my version would silently truncate.”
Someone was spending $200+ a day on Claude Code with no idea where the tokens were going. So they built a terminal dashboard that classifies every session turn into 13 categories. More than half the money was going to conversation, not code. One line install: npx codeburn.
“Great to see someone actually evaluating, sharing data and insights over the hundreds of "this sucks" posts with zero context. Thanks!”
“Thanks for the context. Quality post.”
“That is cool. Will try it out soon.”
“Interesting! I like it!”
“wait this is actually useful. was literally wondering yesterday why my claude bill was so high when i wasn't coding that much. gonna try this today”
“Visibility is key.”
“Very useful”
“Great tool. Installed via npx, zero friction, immediately useful on a 15-project setup running 170+ sessions/month across Opus and Sonnet. Starred.”
“Confirmed working! Before fix: 0 Gemini sessions detected. After fix: 54 sessions captured, full breakdown intact. Thanks for the fast turnaround on the fix!”
Someone was spending $200+ a day on Claude Code with no idea where the tokens were going. So they built a terminal dashboard that classifies every session turn into 13 categories. More than half the money was going to conversation, not code. One line install: npx codeburn.
“Great to see someone actually evaluating, sharing data and insights over the hundreds of "this sucks" posts with zero context. Thanks!”
“Thanks for the context. Quality post.”
“That is cool. Will try it out soon.”
“Interesting! I like it!”
“wait this is actually useful. was literally wondering yesterday why my claude bill was so high when i wasn't coding that much. gonna try this today”
“Visibility is key.”
“Very useful”
“Great tool. Installed via npx, zero friction, immediately useful on a 15-project setup running 170+ sessions/month across Opus and Sonnet. Starred.”
“Confirmed working! Before fix: 0 Gemini sessions detected. After fix: 54 sessions captured, full breakdown intact. Thanks for the fast turnaround on the fix!”
“Genuinely thank you so much for this. I was able to find where my claude has been opening thousands of terminal sessions and eating up my tokens without me even sending a single message. Super duper helpful”
“Immediate install and use. It's brilliant, thank you OP!”
“I need this in my life”
“Nice design! Good job!”
“Thanks for making this, will try this out with my team!”
“Codex, Claude Code, Cursor... quietly hiding the real cost of your usage. That's why CodeBurn exists. It tracks tokens, cost, and performance across 18+ AI coding tools, so you can compare models, optimize usage, and see where your budget leaks.”
“beautiful”
“Install codeburn, then run codeburn optimize. That command scans your coding agent sessions for specific waste. Repeated file reads, low read-to-edit ratios, uncapped bash output, unused MCP servers. And returns token-level savings estimates per fix.”
“Four out of six in a single release cycle is genuinely impressive. Per-project drill-down and cost-per-session are exactly what I needed most. Great project.”
“And thanks for the quick fixes!!”
“Genuinely thank you so much for this. I was able to find where my claude has been opening thousands of terminal sessions and eating up my tokens without me even sending a single message. Super duper helpful”
“Immediate install and use. It's brilliant, thank you OP!”
“I need this in my life”
“Nice design! Good job!”
“Thanks for making this, will try this out with my team!”
“Codex, Claude Code, Cursor... quietly hiding the real cost of your usage. That's why CodeBurn exists. It tracks tokens, cost, and performance across 18+ AI coding tools, so you can compare models, optimize usage, and see where your budget leaks.”
“beautiful”
“Install codeburn, then run codeburn optimize. That command scans your coding agent sessions for specific waste. Repeated file reads, low read-to-edit ratios, uncapped bash output, unused MCP servers. And returns token-level savings estimates per fix.”
“Four out of six in a single release cycle is genuinely impressive. Per-project drill-down and cost-per-session are exactly what I needed most. Great project.”
“And thanks for the quick fixes!!”
