{"version":"2.1.248","anchor":"one-hour-prompt-cache-decision-reworked-around-overage","canonical_anchor":"one-hour-prompt-cache-decision-reworked-around-overage","heading":"One-hour prompt cache decision reworked around overage","tier":"internal","area":"Caching","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/one-hour-prompt-cache-decision-reworked-around-overage","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### One-hour prompt cache decision reworked around overage\n\nWhether a one-hour prompt cache is allowed can now be overridden per agent and can ignore overage.\n\n**What**\n\nThe 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.\n\n**Details**\n\n- The allowlist of contexts permitted a one-hour cache comes from remote config, with a compiled fallback of `repl_main_thread*`, `sdk`, `auto_mode` and `memdir_relevance`.\n\n**Evidence**\n\n`tengu_prompt_cache_1h_config`\n\n- Flag `tengu_prompt_cache_1h_config`: Not enough to say (read for one account on one subscription tier against v2.1.248; this account: no value returned, anonymous baseline: no value returned, compiled default: not a boolean we can read)\n- Area: Caching\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5"}