Prompt caching matches an exact prefix, so a change high up recomputes everything below.
The order is system prompt and tools, then project context, then conversation. That is why mid-session changes to the top cost money.
One at a time. Tell it whether you knew, and the ones you did not stay in your pile.
The order is system prompt and tools, then project context, then conversation. That is why mid-session changes to the top cost money.
The order is system prompt and tools, then project context, then conversation. That is why mid-session changes to the top cost money.
Each model has its own, and the CLI asks for confirmation only while the cache is still warm.
That holds for Opus 5.5, Sonnet 5.5, Haiku 5.5 and Fable 5.1. On most other models it does not.
/usage shows a prompt cache line with hit ratio and warm or cold state.If costs look odd, this line says whether the cache is working and names a likely cause when it is not.
90 percent of users stay under 30 USD a day. Use it as a baseline for your own usage.
That is when teammates run in plan mode. Parallel agents multiply cost.
On Opus 5.5, Sonnet 5.5, Haiku 5.5 and Fable the model always thinks, so MAX_THINKING_TOKENS does nothing there.
It is not a different model. Enable it at the start of a session, because the first enable reads the whole conversation uncached.
Recaps, idle compaction, prompt suggestions, loops and goal check-ins all use some. CLAUDE_CODE_GOAL_CHECKIN_MINUTES=0 turns off goal check-ins.
API keys, cloud providers and usage credits get five minutes, and so do subagents.