SpinUp Forge · Token burn

AI usage by day, source, and work driver.

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

Data through 2026-09-13 · last extracted 2026-09-13

Claude Code turns132,069assistant turns
Active days133rows in view
Measured non-cache floor1.8BCodex split unavailable
Context processed33.7Bincl. cached re-reads

Daily burn

Heatmap

Weekly trend

Log-scaled trend

Source split

Exact beside estimated

exact1.6BCodex / 5%
exact30.4BClaude Code / 90%
exact645.7KPerplexity Sonar / 0%
estimated52.4KChatGPT / 0%
estimated1.6BLocal · MLX / 5%
estimated1.7KLocal · Ollama / 0%

Read Claude Code as context throughput, not spend. Its observed uncached input plus generated output is 0.5% (137.4M); the remainder is cache creation and cache reads. ChatGPT is visible text only; MLX reports prompt tokens only. Codex composition is unavailable, so its processed total is excluded from the non-cache floor.

Drivers

What is burning tokens

research57%
review35%
shipping7%
planning0%

Claude Code by estate

Foundry (harness)90%
KF (Knowledge Forge)8%
Council2%
Other1%

Scale equivalents

Make the number human

Measured non-cache floor — excludes Codex

Approx. words1.3Btokens × 0.75 words
Reading time89,059 h250 words per minute
Novel equivalents14,84390k words per novel

If every token were a written word

1.3B words

1.8B measured non-cache tokens × 0.75 · excludes Codex

That is 14,843 novels — each book below = 248 novels

2,276× the length of War and Peace

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

1.3B words ÷ 90,000 words/novel = 14,843 novels · 2,671,764 printed pages (÷ 500 words/page) · ÷ 587,000 words (War and Peace) = 2,276×

Reading it aloud at 250 words/min

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

1.3B words ÷ 250 wpm ÷ 60 = 89,059 h · 2,226 work-weeks · 45 working years · 11,132 eight-hour days

Day detail · peak day

2026-09-11

research

Total burn2.7B
Claude Code2.5B9,390 responses · 0.5% uncached input + output
Codex170.5M
ChatGPT00 visible responses · text estimate
Local · MLX51.4M86,899 req · floor
Local · Ollama0
Estate (CC)KF 0% · Foundry 100% · 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 callsSonarexactChatGPTest · KMLXest · MOllamaestDriver
2026-09-13127.1964.958.836.031300.032.30research
2026-09-12379.81,067.7320.35.34200.054.20research
2026-09-112,739.31,118.5170.52,517.49,39000.051.40research
2026-09-101,709.1824.668.41,589.98,40300.050.70research
2026-09-09566.6676.196.8409.02,42900.060.80research
2026-09-08321.1647.010.1253.01,69700.058.00research
2026-09-07911.2747.819.6834.55,24100.057.10review
2026-09-06847.0810.65.9775.65,18300.065.50research
2026-09-05735.4763.11.6679.43,15900.054.40research
2026-09-04681.7717.61.0634.61,84600.046.20research
2026-09-03670.0675.318.5601.42,12200.050.20research
2026-09-02362.3622.31.1298.91,27900.062.30research
2026-09-011,027.3587.04.3968.14,34400.055.00review
2026-08-311,350.4461.471.61,222.63,69100.056.20research
2026-08-30514.3298.549.2410.21,87200.055.00research
2026-08-29417.1325.53.3354.21,05200.059.60research
2026-08-28385.5462.510.1326.21,43200.049.20review
2026-08-27298.8531.90.0248.71,35100.050.10research
2026-08-26115.5580.14.660.250500.050.70research
2026-08-25148.4630.90.397.565200.050.60research
2026-08-24209.8662.10.0156.684500.053.20research
2026-08-23703.7719.5103.5543.12,40100.057.10review
2026-08-221,376.1745.930.71,288.55,42301.056.90shipping
2026-08-21871.3630.627.1788.44,67400.055.80review
2026-08-20636.3573.973.5512.22,57500.050.60research
2026-08-19470.5575.88.8414.62,62300.047.10review
2026-08-18366.8539.414.0303.61,19403.249.10research
2026-08-17612.1571.03.9552.42,27600.055.80research
2026-08-16888.6575.024.3808.53,36800.655.80research
2026-08-15568.8534.59.7504.11,97100.055.10research

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.