A thread going around says Claude Code limits "leak" because every message re-sends the whole conversation. The mechanics are real, and Anthropic's cost documentation confirms them: usage climbs in long sessions because the full conversation goes along with each request, and cache misses happen after a break longer than the cache lifetime. What is new is that you can now see it. This post reads the line, then goes through five fixes the docs recommend.
Read the Prompt cache line
Run /usage. On Claude Code v2.1.251 or later, once the main conversation has its first API response, the Session block includes a Prompt cache line. The docs show this sample:

Prompt cache (main): 14 requests · 91% of input tokens from cache · 2 misses (last 6m 10s ago, 310.2k tokens re-cached) · 1 expected rebuild (compaction or tool-result clearing) · warm (1h TTL, last activity 40s ago)
What each part means, per the docs:
- Hit share: the percentage of input tokens served from cache. Higher is better.
- Misses: requests that re-processed content the cache already held, with the time of the last one and how many tokens were written back to cache. From v2.1.260 the line can name a likely cause, such as changed tool definitions.
- Expected rebuilds: misses Claude Code caused itself, by compaction or by clearing old tool results. Counted separately.
- Warm or cold: whether the cached prefix is still inside its lifetime. When cold, the line shows how long the session has been idle.
Two limits to know. It covers the main conversation only, not subagents, and /clear resets it. The 91% and 310.2k figures above are the page's example, not benchmarks. Dollar totals in the Session block (the page's sample shows a $0.55 total) are estimates computed locally from token counts, and the page says that block is intended for API users; subscribers see plan usage bars instead.
A habit that costs nothing: glance at the line before you walk away. If it says warm with a short TTL left, a quick follow-up is cheap. If it says cold, the next message rebuilds the prefix.
Fix 1: clear between tasks
The docs: use /clear to start fresh when switching to unrelated work, because stale context wastes tokens on every later message. Name the session first with /rename and come back with /resume if you need it. Compaction is not free either: /compact reads the conversation it summarises, so compacting a huge context is itself a large request. When you want a fresh start rather than continuity, /clear costs nothing.
Fix 2: keep CLAUDE.md small, move workflows into skills
CLAUDE.md is loaded at session start, so its tokens ride along even for unrelated work. The docs advise keeping it under about 200 lines with essentials only, and moving detailed workflows (their examples are PR reviews and database migrations) into skills, which load only when invoked. If you are on a plan, /usage can also show rows like "Trim your CLAUDE.md" with its token cost per request.

Fix 3: pick the model and effort on purpose
The docs say Sonnet handles most coding tasks well and costs less than Opus, which they reserve for complex architectural decisions or multi-step reasoning. Switch with /model or set a default in /config. Extended thinking is on by default and thinking tokens are billed as output tokens, so lower the effort with /effort for routine work. On models with a fixed thinking budget you can set MAX_THINKING_TOKENS (the page's example is 8000); adaptive-reasoning models ignore nonzero budgets, so use effort levels there. For simple subagent tasks, set model: haiku in the subagent's configuration.



