How Claude Code uses prompt caching changedprompt-caching
Nearest release: v2.1.240, published 9 hours after this site recorded the change. Shown because the two are within 24 hours of each other. Nothing here says the release caused the edit.
Recorded here
Lines+1added
Lines−4removed
From line
79
where the diff opens
First seen
14 Aug 2026
this site's first read of the page
Recorded edits52to this page, all time
The whole hunk
from line 79, old and new numbered
/
from line 79
7979
8080Each model has its own cache. Switching with [`/model`](/docs/en/model-config#setting-your-model) means the next request reads the entire conversation history with no cache hits, even though the content is identical.
8181
82When you run `/model` at the terminal, Claude Code asks you to confirm the switch only while the current cache hasn't expired. Whether the cache has expired depends on how long it has been since Claude Code last sent a request in this conversation or Claude last responded:
83
84* **Less than one [cache TTL](#cache-lifetime) ago**: the cache is still warm.
85* **One cache TTL or longer ago**: the cache has already expired, so Claude Code switches without asking.
82When you run `/model` at the terminal, Claude Code asks you to confirm the switch only while the cache is still warm. The cache stays warm for one [cache TTL](#cache-lifetime) after Claude Code last sent a request in this conversation or Claude last responded. Once that time passes, the cache has expired, so Claude Code switches without asking.
8683
8784Before v2.1.238, Claude Code didn't check the cache TTL and asked even after the cache had expired.
8885
No line in this hunk matches that.