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-06-15 · last extracted 2026-06-14

Claude Code turns77,729assistant turns
Active days58rows in view
Real input + output486.4Mwork floor, excl. cache
Context processed16.5Bincl. cached re-reads

Daily burn

Heatmap

Weekly trend

Log-scaled trend

Source split

Exact beside estimated

exact23.3MCodex / 0%
exact16.2BClaude Code / 98%
exact166.6KPerplexity Sonar / 0%
estimated285.1MLocal · MLX / 2%
estimated1.7KLocal · Ollama / 0%

Read Claude Code as context throughput, not spend. Only 1.1% (177.8M) 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

shipping61%
research15%
review12%
planning12%

Claude Code by estate

KF (Knowledge Forge)41%
Foundry (harness)34%
Council19%
Other6%

Scale equivalents

Make the number human

Real input + output only — excludes cached re-reads

Approx. words364.8Mtokens × 0.75 words
Reading time24,318 h250 words per minute
Novel equivalents4,05390k words per novel

If every token were a written word

364.8M words

486.4M real tokens × 0.75 · excludes cached-context re-reads

That is 4,053 novels — each book below = 68 novels

621× the length of War and Peace

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

364.8M words ÷ 90,000 words/novel = 4,053 novels · 729,547 printed pages (÷ 500 words/page) · ÷ 587,000 words (War and Peace) = 621×

Reading it aloud at 250 words/min

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

364.8M words ÷ 250 wpm ÷ 60 = 24,318 h · 608 work-weeks · 12 working years · 3,040 eight-hour days

Day detail · peak day

2026-05-30

shipping

Total burn1.4B
Claude Code1.4B7,212 turns · 3.0% real I/O
Codex0
Local · MLX13.4M26,379 req · floor
Local · Ollama0
Estate (CC)KF 82% · Foundry 18% · 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 · KClaude Codeexact · MCC callsSonarexact · KMLXest · MOllamaest · KDriver
2026-06-150.0500.80.00.000.00.00.0planning
2026-06-14890.0648.8490.9874.94,51332.014.50.0shipping
2026-06-13491.6534.63,107.9475.61,9658.312.80.0planning
2026-06-12795.5466.7726.2782.04,5441.012.80.0shipping
2026-06-11185.6368.8464.2174.11,0270.011.00.0planning
2026-06-10624.8421.01,747.9610.22,7040.012.90.0planning
2026-06-09518.4395.6604.2507.92,71545.09.90.0planning
2026-06-081,035.4373.20.01,022.24,2620.013.21.7shipping
2026-06-0790.6257.10.082.177717.78.50.0review
2026-06-0616.3414.60.07.81020.08.50.0planning
2026-06-05110.3609.2505.6100.41,2480.09.40.0shipping
2026-06-04550.9777.7102.2540.82,7240.010.10.0shipping
2026-06-03447.0747.5358.4437.72,1110.09.00.0shipping
2026-06-02361.9725.10.0353.11,6020.08.90.0shipping
2026-06-01222.7756.50.0214.51,1350.08.20.0review
2026-05-311,193.1760.40.01,183.24,85920.99.90.0shipping
2026-05-301,378.6591.80.01,365.37,2120.013.40.0shipping
2026-05-291,289.3432.10.01,279.44,6280.09.90.0shipping
2026-05-28339.9361.40.0335.22,1890.04.80.0shipping
2026-05-27289.7353.60.0285.81,2080.03.90.0review
2026-05-26581.7398.70.0576.72,4420.05.00.0research
2026-05-25250.0368.70.0247.41,0000.02.60.0research
2026-05-2412.9335.50.011.916023.11.00.0planning
2026-05-23261.4345.145.8258.61,6430.02.70.0review
2026-05-22793.9308.11,243.6789.62,5620.03.10.0shipping
2026-05-21285.4205.30.0284.41,8590.01.00.0shipping
2026-05-20605.7199.6103.0601.92,8680.03.70.0shipping
2026-05-19371.7149.60.0369.21,2750.02.50.0research
2026-05-1817.8101.20.017.61590.00.20.0planning
2026-05-1779.8100.50.079.632918.60.20.0research

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.