What
The code that decides whether a one-hour prompt cache lifetime is allowed now takes options, including an agent-level override and a flag to ignore cache overage, and computes overage once rather than per lookup.
Details
- The allowlist of contexts permitted a one-hour cache comes from remote config, with a compiled fallback of
repl_main_thread*,sdk,auto_modeandmemdir_relevance.
Evidence
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Feature flag
tengu_prompt_cache_1h_config Not enough to sayNothing here resolved what this flag was doing on this version, so nothing here should be read as on or off.
This account: no value returned · anonymous baseline: no value returned · compiled default in v2.1.248: not a boolean we can read
Read once, for one account on one subscription tier, against v2.1.248. It isn't a statement about your account. What a flag value here can and cannot tell you
Flag reading moved
The flag server now returns {"allowlist":["repl_main_thread*","sdk","auto_mode","rolling_compact","memdir_relevance","agent_classifier","prompt_suggestion","away_summary","extract_memories"]} for tengu_prompt_cache_1h_config, read as this account.
A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.
Flag reading moved
The flag server now returns nothing at all, having stopped carrying it for tengu_prompt_cache_1h_config, read as this account.
A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.