Follow Discord
Sweep 02 Oct 2026 · 18:55Z Build v2.1.288 509 read Stable v2.1.285 Latest v2.1.287 Next v2.1.288 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.288 ·

Prompt cache keepalive for resumed sessions

Resumed sessions can keep the 1-hour prompt cache warm on a timer, but only when server config sets resumeTouches

Group of 2 Use it now Notable No documentation found Improvements
JSON All of v2.1.288
Use it nowTier: how much it should matter to you
3Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
Prompt CachingArea: what it touches
ImprovementsKind: in v2.1.288,
What probably matters to youSection of the release

What

The prompt cache lets the API reuse earlier parts of a conversation so replies come back faster and cost less. Claude Code can keep that cache warm by touching it on a timer. A resumed session is an earlier conversation you have reopened.

  • New code keeps the 1-hour prompt cache warm for resumed sessions by touching it on a timer.
  • It applies only to subscribers with a 1-hour cache lifetime, and only when server config sets resumeTouches.
  • Without resumeTouches, the keepalive stops for resumed sessions with the reason resume_touches_off. Before, there was no special check for resumed sessions.

Why

When it is enabled, a resumed conversation is less likely to lose its cache, which could mean fewer cache misses after you come back to it. When it is not enabled, resumed sessions do not keep the cache warm this way.

Read from
Names in the bundleresumeTouches
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 doubtIt is not clear where `resumeTouches` is set or whether you can change it yourself.

See this entry in the whole of v2.1.288 →

Feedback