PRODUCTION SCENARIO
A long customer session sets the top-level effort parameter on every request. The app caches a 40,000-token system prompt and switches effort from high to low for follow-up turns, after which cache reads drop to zero.
What should the app do?
Answering here is anonymous. Nothing is saved unless you sign in.
Show answer and explanation
Answer: Choose one effort level at the start and hold it across the cached conversation
Top-level effort shapes the rendered prompt, so changing it between requests invalidates cached prefixes. The effort page says to hold top-level effort constant within cached conversations and vary it across workloads instead; TTL and breakpoints do not change that invalidation.
Official Source: https://platform.claude.com/docs/en/build-with-claude/effort ↗