Headroom Daily: Fixing Inflated Savings Numbers
Headroom corrected systematically overstated savings and spend, with pricing now tied to actual cache mix and rejected turns excluded from totals. Compressor work focused on the same theme: stop silent data loss and handle uncompressible content gracefully.
Duration: PT2M28S
Episode overview
This episode is a short developer briefing from Headroom Daily.
It explains recent repository work in plain language.
- Show: Headroom Daily
- Published: 2026-09-21T22:00:32Z
- Audio duration: PT2M28S
Transcript excerpt
This excerpt keeps the crawler page concise. Listen to the episode or use the RSS feed for the full update.
Good morning, it's Monday, September 21st, 2026.
The lead story: Headroom's cost numbers were too high, and today's work makes them honest.
First, savings are now priced against what you would actually have paid. Change 89a58fd and pull request 3699 found the old math used full list price for every token saved. After the first request in a cache window, those tokens would have been cheap cache reads — a tenth of list on Anthropic and Gemini, half on…
Related: pull request 3615 stops rejected turns from feeding the funnel. Previously only server errors were excluded. Now any provider rejection at 400 and above goes to failed or rate-limited counters, not spend. The real case: 13 rejected over-length turns added 23.7 million tokens and 242 dollars that were never…
Second theme: compressors that do less harm. Pull request 3648 stops the smart crusher from dropping JSON object properties while keeping large-array compaction. Pull request 3685 adds last-resort elision for dense machine lines — minified bundles, encoded blobs — keeping head and tail with a retrieval marker. In…
What's next: expect lower but defensible savings totals after migration, and watch open proposals to keep…
Nearby episodes from Headroom Daily
- Proxy Coexistence and Restart Reliability
- Gateway Expands to Codex, Beacon Gets Leaner
- The Cost of "Lossless"
- False Positives, Fence Escapes, and False Savings
- When Two Fixes Collide
- Cross-Protocol Routing and Correctness Fixes
- The Cost of Things Silently Falling Through
- When Identity Isn't Display Text