
What happened
Anthropic posted guidance saying Claude Code's output tokens cost about 5 times its input tokens, and that one long session costs more than splitting the same work into short sessions.
Why it matters
Agentic coding tools bill per task, not per subscription, so how a session is run directly changes what teams pay — cache reads cost 0.1× input, while restoring a broken cache can cost up to 2× input.
What to watch
The savings hinge on whether prompt caches survive, since they expire one hour after last use or 5 minutes after the API key's last use; watch whether teams adopt Anthropic's advice to set /model and /effort at session start.
WHO IT HITSDevelopers and engineering teams running Claude Code who pay per token are the ones whose monthly spend this guidance speaks to; the fixes Anthropic suggests, like clearing context between tasks and setting the model at session start, are actions an individual engineer takes, not a platform setting.
Summaries like this, every morning.
Anthropic's post draws a distinction that matters for anyone paying per token: subscription-style coding tools hide the cost of a request, but agentic tools like Claude Code price each task separately. The post walks through where those tokens go, splitting the work into a prefill phase and a decode phase. In prefill, the model reads the request, the context, the system prompt, CLAUDE.md, the message, and everything added to the conversation since the last message, including files Claude read and command output. In decode, output tokens — the thinking, tool calls, and text — are generated one at a time.
Much of the guidance circles back to the prompt cache, which Anthropic describes as the mechanism that keeps costs down. A cached read costs 0.1 times the input price, and a write to the cache costs up to 2 times the input price but happens only once per token. Anthropic warns that user actions can invalidate the cache anyway: caches require a match at the start of the request, so switching models or effort levels mid-session, switching permission modes, running /compact, or simply leaving time to pass can force the whole conversation to be re-read at full price. The one-hour expiry after last use and the five-minute expiry after the API key's last use are the main culprits.
Anthropic's summary names four factors to watch as having the biggest effect on cost: long sessions, carrying too much context, using a larger model or higher effort level than the task needs, and a broken prompt cache. The practical suggestions — running /clear between unrelated tasks, setting /model and /effort before starting, attaching files rather than asking Claude to read them, checking /context early, and running /compact before the cache expires — all push in the same direction. Whether they bring bills down in practice is likely to depend on how carefully individual engineers follow the session-start advice, since the cheapest path Anthropic describes (cache reads at 0.1 times input) is also the easiest to lose to a mid-session change.
Pick your industry and the AI tools you use, and get news related to your work every day.
Free · 30 seconds with Google · unsubscribe anytimeWhat is AIToday? →
Ask AI anything about this article. The AI reads this article, earlier AIToday articles, and Wikipedia, and cites its sources. Q&As are published on this page for other readers too.
On October 21, 2026, Anfini CEO Jun Hashimoto gave a special lecture at Meiji University's engineering faculty…

On November 3, voters in 10 states backed restrictions on data center development in 40 of 41 local ballot mea…

Numica, which buys small accounting practices from retiring owners and runs the work on its AI software, has r…

A six-year web designer who signed up for Claude Pro in April 2026 and later moved to Max published the first…

In one session that ran 13 days and 5,065 requests, a single request late in the session cost about $0.42 agai…

EC自動化工房 laid out four things to standardize before AI translation, using a sample mug "350ml" that mixed unit…
