Follow Discord
Sweep 03 Nov 2026 · 22:27Z Build v2.1.318 536 read Stable v2.1.311 Latest v2.1.318 Next v2.1.318 Feeds RSS JSON llms.txt llms-full.txt Unofficial
HomeReleasesv2.1.317entry #426

Claude Code v2.1.317 ·

Resumed sessions may ask for a longer prompt cache

When you resume a session whose last reply used a 5-minute prompt cache, Claude Code may record a request for a 1-hour cache

Under the hood Internal Changes
JSON All of v2.1.317
Under the hoodTier: how much it should matter to you
1Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
Prompt CacheArea: what it touches
Internal ChangesKind: in v2.1.317,
Internal ChangesSection of the release

Unclear What the recorded 1-hour request changes for a resumed session is not clear.

What

The prompt cache keeps recent conversation content on the server so it does not have to be processed again. It can last 5 minutes or 1 hour. When you resume a session and the last reply used the 5-minute cache, Claude Code may now record a request to move to the 1-hour cache. It does this only when all of these hold:

  • a model is known for the session
  • the saved entry did not come from a remote source
  • the session was not forked from another one
  • a 1-hour cache is available
Why

This concerns how long cached content lasts when you pick a session back up.

How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtWhat the recorded 1-hour request changes for a resumed session is not clear.

See this entry in the whole of v2.1.317 →

Feedback