menu bar · macOS

BurnRate

What you are consuming in Claude Code, by project, agent and day.

Reads your local Claude Code transcripts and shows token consumption, estimated in dollars at list API prices, broken down by project, agent, session, model and hour. It is a comparable estimate, not your bill.

Launch price · −50%Final price €48

€24+ VAT at checkoutLicence agreement

392 licences left at the launch price

Follow BurnRate on X · @burnratemac

illustrative pace, not real usage

The figure is not a bill. On a Max or Pro subscription you do not pay per token, so there is no real amount to show. What you see is an estimate at list prices — useful for comparing projects and seeing the trend, not for reconciling a statement.

The problem

You know the cost of one session. Not the month's.

Claude Code tells you the cost of one session. It will not tell you which of the thirty projects you touched this month ate half the total.

And if you run several agents in parallel across several accounts, you have no overall picture at all.

From a file on disk to a rate in the menu bar

Five steps, in the order they actually happen.

01ScanReads the JSONL lines across all four .claude* folders on your Mac, not just the active account.
02ExtractTakes only the tokens, the model, the agentId and the timestamp. Conversation content is never touched.
03AggregateGroups them by project, agent, session, model, day and hour, from one core, used by both the window and the nine MCP verbs.
04PriceConverts tokens to dollars at list API prices. A model with no price in the table shows as unknown, never as zero.
05ShowThe current rate sits in the menu bar, illustrative. The full breakdown lives in a navigable window, using the same figures.
// screens

The app's screens

Sub-agents get their own lines instead of being folded into the main session, so you see which agent spent the day.
BurnRate adds up the tokens and an estimated cost for each project, so the expensive one stands out.
Today splits the day by hour and by model, and a model with no known price is flagged and left out, never counted as zero.
Today's cost sits in the menu bar, and a click shows the current rate, estimated at API list prices, with the top agents and projects.
// screen tour

What each screen shows

  1. 01 / 04

    Sub-agents, each on its own line

    • At the top, the day's cost is split between the main session and the sub-agents, with each one's share. The toggle switches from today to all history.
    • The ranking puts every agent on its own line, with its project, requests, tokens and cost, instead of folding it into the main session.
    • A cost that includes requests with no known price is shown with "≥": marked as a minimum, not silently rounded down.
    • It matters because 58% of usage lines come from sub-agents: "why did today cost that much" is answered by agent, not by project.
  2. 02 / 04

    Projects, with worktrees folded onto the repo

    • For each project, BurnRate adds up the requests, the tokens and an estimated cost, so the expensive one stands out.
    • Worktrees and subdirectories are folded onto the repo root, and the line under the name says what was folded: "includes worktrees", "includes subdirectories".
    • At the top you see how many projects remain after grouping and how many there would be without it. The "Show the raw breakdown, by exact cwd" toggle shows the raw split, by exact directory.
  3. 03 / 04

    The day, by hour and by model

    • The day's total carries "≥" and a note saying how many requests with no known price are not included: the unpriced model is flagged and left out, never counted as zero.
    • "Rate by hour" splits the day by hour, with each hour's requests and cost. Hours with no activity stay empty, not zero.
    • Next to it, yesterday, the median of the last 7 full days and the mean per active day give today's figure a reference.
    • "Today's models" lists the day's models with their request counts, the unpriced one included.
  4. 04 / 04

    The menu bar

    • Today's cost sits right in the menu bar. A click shows the current hourly rate, next to yesterday at the same time.
    • Agents come before projects, with the sub-agents' share, because the day's question is usually answered by agent.
    • The note "Estimate from usage × list API prices. Not a bill." stays at the bottom: the figure is an estimate at list prices, not your bill.
    • "Open window" opens the window with the full breakdown, on the same figures.

What it does

Once you work heavily with Claude Code, the question "where did it go" comes up early. Which project consumes most? Which agent? What happened on Tuesday?

BurnRate reads the transcript lines Claude Code leaves on disk, across all your accounts, and extracts only the usage numbers — never the conversation content. It aggregates them by project, agent, session, model, day and hour, and converts them to dollars using list API prices.

When a model has no price in the table, its usage shows as unknown rather than zero. The difference matters: a total marked "at least this much" is honest; one that stays silent about what it does not know is not.

The current rate sits in the menu bar. The full breakdown is in a navigable window. It also ships an MCP bridge with nine verbs that reads straight from disk and answers with the app closed.

Note on language: the interface and the MCP responses are in Romanian. There is no language switch yet.

What it shows

Four angles on the same usage

Breakdown

02
  • Usage broken down by project, agent, session, model, day and hour
  • Reads every Claude account on your Mac, not only the active one

Numeric honesty

02
  • What cannot be computed shows as unknown, never as zero
  • Extracts usage numbers only — it does not read conversation content

Live access

02
  • Current rate in the menu bar
  • MCP bridge with nine verbs that works with the app closed

Privacy & language

02
  • Never writes to or modifies your Claude Code files
  • The interface is in Romanian

The licence

One licence, one Mac

The date range and exporting the figures need an activated licence; the rest of the app works without one.

Needs an activated licence

  • The date range
  • Exporting the figures: CSV, every breakdown

Activation

  • The licence is activated online: me-digital.ro receives the key, a machine identifier and the Mac's name.
  • At launch, the app asks whether the seat is still active.
  • Your usage is not reported: no filenames, no project names, no figures.
  • The app asks for no extra system permission (its entitlements file is empty).

Why you can trust it

Five things the app does exactly as described here.

58% comes from sub-agents

Measured on real data: 58% of usage lines come from sub-agents, not the main session. Tools before this one silently folded agentId onto the parent session. BurnRate is the only one that reads it in every verb, not just one dedicated to it.

Unknown, never zero

When a model has no price in the table, its usage shows as unknown, not as zero. A total marked "at least this much" is honest; one that stays silent about what it doesn't know is not.

One source of truth

The window and the nine MCP verbs read from the same core. No verb recomputes anything on its own, so they can never land on two different figures for the same question.

169 tests, on real defects

The suite covers exactly the defect classes hit on real data: the 1.34 MB line, the zero that hides an unknown, nondeterministic assignment on fold, the agent's name. Across 32 suites.

Notarised by Apple

The build you download is signed with a Developer ID and notarised by Apple: Gatekeeper accepts it on first launch, with no warning.

Honesty

The limit you should know about

A real limit, not a footnote.

It depends on Claude Code's format

BurnRate reads the JSONL files Claude Code writes today for its own purposes, not a published, documented API. If that format changes, reading it can stop working overnight. That is why the price on this page is a one-time purchase, not a subscription: a subscription would be a promise of ongoing maintenance on ground we don't control.

Requirements

System
macOS 14.0 or later
Processor
Universal binary: Intel and Apple silicon
Licence
One payment, no subscription. One licence, one Mac

Frequently asked questions

No. On a Max or Pro subscription you do not pay per token, so there is no real amount to show. What you see is an estimate at list prices, useful for comparing projects and trends, not for reconciling a statement.

It doesn't show real usage. It's illustrative, a decorative animation with no reading behind it. Real usage lives in the app window and the menu bar, not in the gauge at the top of the page.

Because 58% of usage lines come from sub-agents, and the tools that came before this one silently folded them onto the main session. The question "why did today cost that much" gets answered by agent, not by project.

Reading it can stop working overnight, because BurnRate depends on a format it doesn't control. That is why the price is a one-time purchase, not a subscription.

Yes. The build you download is signed with a Developer ID and notarised by Apple: Gatekeeper accepts it on first launch, with no warning.

Purchase

BurnRate for Mac

Built with

SwiftSwiftUIMCPmacOS
Launch price · −50%Final price €48
€24

+ VAT, calculated at checkout for your country

392 licences left at the launch price

Licence agreement

Activation

How to activate your licence

Download the app

Download version 1.0.2

4.1 MB

Open the app, click “Activate licence” in the toolbar, paste the key from the email and press Activate.

On X

What BurnRate has posted on X. Each post opens on X.