Prompt Cache Pitfalls

Claude Code caches the conversation so each new turn only pays full price for the new tokens. Several mid-session switches throw that cache away. The deeper into a session you are, the more it costs.

Switching models

Each model has its own cache. After /model, the next request reads the entire conversation history with no cache hits.

That means the “sensible” move of dropping to Haiku for a quick question 100k tokens into an Opus session is often more expensive than letting Opus answer. You pay to build a Haiku cache for the full context, then pay again to rebuild the Opus cache when you switch back.

Pick the model at the start of a session, or use /branch or /btw for cheap side work instead of switching.

Switching effort

The cache is keyed by effort level as well as model. Changing /effort mid-session has the same cost as a model switch.

Turning on fast mode

Fast mode (/fast) runs Opus at up to 2.5x speed at a higher per-token price. Three things to know before toggling it:

1. It bills to usage credits, not your plan. On Pro, Max, Team, and Enterprise it is only available through usage credits and draws from them even if you have plan usage left.
2. It persists across sessions. Once on, it stays on in new sessions until you run /fast again. Set "fastModePerSessionOptIn": true in settings if you want each session to start with it off.
3. Enabling it mid-conversation re-bills the whole context. The first time fast mode turns on in a conversation you pay the full fast-mode uncached input price for everything already in context. This happens once per conversation, so toggling off and on again later does not repeat it.

If you want fast mode, turn it on before the first message.

Rule of thumb

Decide model, effort, and fast mode at the start. Changing any of them later is a one-time charge proportional to how much context you have built up.

Run /context to see how much that is before you switch.