Whether a one-hour prompt cache is allowed can now be overridden per agent and can ignore overage.
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
What's wrong with this entry?
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.
- 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.
tengu_prompt_cache_1h_config
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.