SpinUp Forge · Token burn

AI usage by day, source, and work driver.

Exact local logs for Codex and Claude Code, labelled estimates for local models — bucketed by London day and pointed at one question: what should the computer do next?

Data through 2026-07-30 · last extracted 2026-07-30

Claude Code turns97,227assistant turns
Active days98rows in view
Real input + output1.6Bwork floor, excl. cache
Context processed23.3Bincl. cached re-reads

Daily burn

Heatmap

Weekly trend

Log-scaled trend

Source split

Exact beside estimated

exact285.5MCodex / 1%
exact21.8BClaude Code / 94%
exact525.0KPerplexity Sonar / 0%
estimated1.2BLocal · MLX / 5%
estimated1.7KLocal · Ollama / 0%

Read Claude Code as context throughput, not spend. Only 0.7% (145.3M) is real input+output; the rest is cached-context re-reads that scale with conversation length. MLX is a prompt-token floor (output unlogged) — true usage is likely 2–4× higher.

Drivers

What is burning tokens

review49%
research35%
shipping15%
planning1%

Claude Code by estate

Foundry (harness)73%
KF (Knowledge Forge)21%
Other4%
Council3%

Scale equivalents

Make the number human

Real input + output only — excludes cached re-reads

Approx. words1.2Btokens × 0.75 words
Reading time81,725 h250 words per minute
Novel equivalents13,62190k words per novel

If every token were a written word

1.2B words

1.6B real tokens × 0.75 · excludes cached-context re-reads

That is 13,621 novels — each book below = 228 novels

2,088× the length of War and Peace

Tolstoy’s novel runs to about 587,000 words — the canonical doorstop.

1.2B words ÷ 90,000 words/novel = 13,621 novels · 2,451,746 printed pages (÷ 500 words/page) · ÷ 587,000 words (War and Peace) = 2,088×

Reading it aloud at 250 words/min

Your token burn, read aloud81,725 h
A 40-hour work-week40 h
A 2,000-hour working year2,000 h

1.2B words ÷ 250 wpm ÷ 60 = 81,725 h · 2,043 work-weeks · 41 working years · 10,216 eight-hour days

Day detail · peak day

2026-07-11

research

Total burn1.9B
Claude Code1.9B6,447 turns · 0.6% real I/O
Codex14.9M
Local · MLX22.0M41,581 req · floor
Local · Ollama0
Estate (CC)KF 92% · Foundry 8% · Other 0%

Project-level detail (commits, top projects) loads only when running locally.

Moving-average table

Last 30 days

Click a row for that day’s detail.

DateTotal · M7d avg · MCodexexact · MClaude Codeexact · MCC callsSonarexact · KMLXest · MOllamaestDriver
2026-07-3092.8532.00.882.26940.09.80review
2026-07-291,368.4551.18.61,325.25,5540.034.60review
2026-07-28898.0445.11.4864.33,5100.932.30review
2026-07-27965.9428.411.6922.32,9380.032.00research
2026-07-26214.6448.51.5187.31,75635.825.80research
2026-07-25114.1551.70.185.46100.028.50review
2026-07-2470.2689.30.041.61710.028.60planning
2026-07-23226.2783.33.8215.61,2060.06.80shipping
2026-07-22626.6811.27.7577.12,18521.841.80research
2026-07-21781.4829.24.4741.93,22914.735.10research
2026-07-201,106.6808.616.81,060.84,5140.029.10review
2026-07-19936.9782.217.2888.14,74735.231.70research
2026-07-181,077.2725.344.91,007.54,8600.024.80review
2026-07-17727.9842.67.7694.92,3160.025.20review
2026-07-16421.9841.22.6393.11,6220.026.20shipping
2026-07-15752.6943.66.3721.33,6168.625.10shipping
2026-07-14636.9968.210.7605.52,3410.020.70shipping
2026-07-13921.8938.01.8896.63,3260.023.40review
2026-07-12538.8965.31.0515.02,99931.622.80review
2026-07-111,898.6974.314.91,861.76,4470.022.00research
2026-07-10717.7841.26.4691.72,7620.019.60research
2026-07-091,138.5828.913.51,105.04,4499.120.10review
2026-07-08925.0685.15.7903.13,3840.016.20shipping
2026-07-07425.7673.31.4407.52,2434.116.80shipping
2026-07-061,113.1636.49.31,085.95,03068.417.80review
2026-07-05601.3502.30.6583.13,47824.217.50review
2026-07-04967.1419.910.8939.04,8644.117.30review
2026-07-03631.3284.23.5609.63,7158.718.20research
2026-07-02132.0203.70.1117.58740.014.40research
2026-07-01842.7209.32.4825.53,56721.914.70research

Method & fidelity

How each lane is counted

Days are bucketed in Europe/London. Exact lanes come from real local logs; estimated lanes are labelled and never presented as exact.

The charts read scrubbed daily totals from data/daily-burn.json (committed). Day-detail (commit counts, project names) is read server-side from the git-ignored private/ file via /api/detail — never bundled into the page or committed, so a deployed build would show none of it. Re-run npm run extract to add a day.