Follow Discord
Sweep 22 Oct 2026 · 04:32Z Build v2.1.308 527 read Stable v2.1.308 Latest v2.1.308 Next v2.1.308 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.286 ·

Prompt cache keepalive added, with a policy that switches it off for HIPAA organizations

Claude Code can ping the API to keep a one-hour prompt cache alive during pauses, unless the allow_cache_keepalive policy denies it

Group of 2 You'll notice No documentation found Improvements
JSON All of v2.1.286
You'll noticeTier: how much it should matter to you
5Useful: my rating, 1 to 5
5Signal: worth watching, 1 to 5
Prompt CacheArea: what it touches
ImprovementsKind: in v2.1.286,
What probably matters to youSection of the release

Unclear It is not known whether cache keepalive is active for ordinary users.

What

The prompt cache lets the API reuse the start of a conversation instead of processing it again. A new module keeps a one-hour cache entry alive by sending a small request to /v1/messages/cache_touch at a regular interval.

  • Settings come from the server-controlled switch tengu_sequential_cloud, which holds touchIntervalSeconds (10 to 120, default 30) and activityWindowMinutes (1 to 1440, default 60).
  • It runs only for subscribers with a one-hour cache lifetime. It does not run in a cloud session, when using overage (usage beyond your plan), or when ANTHROPIC_UNIX_SOCKET is set.
  • The requests carry the header anthropic-cache-keepalive.
  • A new policy entry, allow_cache_keepalive, labelled "Renewing the prompt cache lifetime" (requirement HIPAA-R65), must also allow it. It is denied for hipaa organizations and is denied when the policy cannot be read.

Why

Keeping the cache alive could mean fewer cache misses after idle pauses in long sessions. Organizations under HIPAA rules will not get it. Nothing has been read about tengu_sequential_cloud, so whether keepalive is running is not known.

Read from
Names in the bundleallow_cache_keepalive
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 known whether cache keepalive is active for ordinary users.

See this entry in the whole of v2.1.286 →

Feedback