PulseAugur
EN
LIVE 00:58:13

Claude Code token usage dominated by cache re-reads, costing thousands

By PulseAugur Editorial · [3 sources] ·

A deep dive into Claude Code's token usage reveals that a significant majority of tokens are consumed by cache re-reads rather than new output. One user found that 97% of their 44.6 billion tokens were cache reads, costing an estimated $15,290 if billed at API list prices. Subagents and Bash commands were identified as major drivers of this re-read cost. Additionally, the prompt caching mechanism's Time-To-Live (TTL) can lead to substantial cost increases if a session is left idle, with a 200K token session potentially costing $1.00 for a single follow-up message after a break, compared to $0.04 if the cache remained warm. AI

IMPACT Highlights potential cost inefficiencies in LLM usage and the impact of caching mechanisms on operational expenses.

RANK_REASON User analysis of their own Claude Code token usage and caching behavior.

Read on dev.to — LLM tag →

AI-generated summary · Google Gemini · from 3 sources. How we write summaries →

Claude Code token usage dominated by cache re-reads, costing thousands

How we ranked this

Signal score
0 / 100
Composite score across the factors below. Higher = stronger signal that this story matters right now.
Newsworthiness bucket
Commentary
User analysis of their own Claude Code token usage and caching behavior.
Source corroboration
3 independent sources
Multiple independent publishers reporting the same story raises confidence that it's real and newsworthy.
Topics
infra, product
Editorial topic classification. Feeds into how the story surfaces on /topic/<slug> hub pages and into the per-entity coverage mix.
AI-industry relevance
High
Clearly on-topic for AI-industry coverage.
Story freshness
8 days old
Aged out of breaking-news scoring windows; ranking reflects the durable signal from the full source set.
Coverage growth since scoring
+1 source(s) since last score
New sources have picked up this story since our last re-score. Score will update on the next scoring pass.

Full methodology in our editorial standards.

COVERAGE [3]

  1. dev.to — Claude Code tag TIER_1 English(EN) · StackVersus ·

    A week of my Claude Code logs: where 1.8 billion input tokens went

    <p>I hit Claude Code's usage limits often enough that I wanted to know what was actually filling the context. Claude Code keeps a<br /> transcript of every session on disk (<code>~/.claude/projects/...</code>), with the real API usage of every request. So I read a week of<br /> t…

  2. dev.to — Claude Code tag TIER_1 English(EN) · jidonglab ·

    Claude Code Token Usage: 97% of 44.6B Tokens Were Cache Re-Reads

    <p>Claude wrote 122 million tokens for me last month. To write them, it read 43 billion.</p> <p>I got that ratio by parsing 30 days of my Claude Code token usage straight from the JSONL session logs on my laptop: 192,178 API requests, 889 main sessions and 5,696 subagents. I want…

  3. dev.to — LLM tag TIER_1 English(EN) · Gabriel Anhaia ·

    A 200K-Token Claude Session Left Idle Re-Buys Its Cache: $0.04 Becomes $1.00

    <ul> <li> <strong>Book:</strong> <a href="https://www.amazon.de/-/en/dp/B0GXNNMKVF" rel="noopener noreferrer">Observability for LLM Applications</a> </li> <li> <strong>Also by me:</strong> <em>Thinking in Go</em> (2-book series) — <a href="https://xgabriel.com/go-book" rel="noope…

RELATED ENTITIES

RELATED TOPICS