{"version":"2.1.286","anchor":"prompt-cache-lifetime-tracked-via-tengu-jaunty-charm","canonical_anchor":"prompt-cache-lifetime-tracked-via-tengu-jaunty-charm","heading":"Idle expiry timer built in, with its lifetime set remotely","tier":"soon","area":"Remote Config","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.286\/e\/prompt-cache-lifetime-tracked-via-tengu-jaunty-charm","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.286","markdown":"### Idle expiry timer built in, with its lifetime set remotely\n\nClaude Code now tracks when something was last active and whether a remotely set lifetime has run out; with no remote setting, nothing expires\n\n**Unclear.** What the tracker is used on, and so what would expire, is not known.\n\n**What**\n\nClaude Code has a new idle tracker. It records the last time each item was active and reports whether a set lifetime has passed since then. The length of that lifetime comes from configuration sent by Anthropic's servers. If no configuration arrives, no lifetime is applied and nothing expires.\n\n**Why**\n\nThis looks like groundwork for letting something expire after a period of inactivity, possibly a cache or a session. Without a lifetime from the server it has no effect.\n\n- Flag `tengu_jaunty_charm`: Not enough to say (read for one account on one subscription tier against v2.1.286; this account: no value returned, anonymous baseline: no value returned, compiled default: not a boolean we can read) These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.\n- Area: Remote Config\n- Tier: Nothing to try yet\n- Useful: 2\/5\n- Signal: 3\/5\n- Present in the build but not switched on"}