{"version":"2.1.251","anchor":"cache-write-cost-estimates-pick-between-a-1-hour-and-5-minut","canonical_anchor":"cache-write-cost-estimates-pick-between-a-1-hour-and-5-minut","heading":"Cache-write cost estimates pick between a 1 hour and 5 minute TTL","tier":"notice","area":"Cost Tracking","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.251\/e\/cache-write-cost-estimates-pick-between-a-1-hour-and-5-minut","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.251","markdown":"### Cache-write cost estimates pick between a 1 hour and 5 minute TTL\n\nCost estimates now pick the cache lifetime that actually applied, so numbers match reality.\n\n**What**\n\nCost estimation now chooses a one-hour cache lifetime when a longer-TTL override is configured or the request comes from the interactive session's main thread, and five minutes otherwise, so estimates match the cache tier actually used.\n\n**Evidence**\n\n`return nM(\"repl_main_thread\") ? \"1h\" : \"5m\";`\n\n- Area: Cost Tracking\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}