{"version":"2.1.311","anchor":"max-age-resolver-for-a-cachesession-setting-with-tengu-ros","canonical_anchor":"max-age-resolver-for-a-cachesession-setting-with-tengu-ros","heading":"New adjustable maximum age, settable by environment variable or by the server","tier":"internal","area":"Settings","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311\/e\/max-age-resolver-for-a-cachesession-setting-with-tengu-ros","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311","markdown":"### New adjustable maximum age, settable by environment variable or by the server\n\nClaude Code gained a maximum-age limit read from an environment variable or the server, with a 90-minute floor on the server value\n\n**Unclear.** What the maximum age applies to, and which environment variable sets it, is not stated.\n\n**What**\n\nClaude Code has a new maximum-age limit. It takes the value from an environment variable first. If that is not set, it uses a number sent by the server, which is accepted only if it falls within a set range. The lowest allowed server value is 5,400,000 milliseconds, which is 90 minutes.\n\nThe limit is skipped in two cases:\n\n- when a server-controlled switch is on; that switch counts as on if the server sends nothing, so by default no limit is applied\n\n- when the session was started by a remote cowork trigger\n\n**Why**\n\nThis gives a time limit on something in Claude Code that the server can tune. As built, the limit is not applied unless the server switch is turned off.\n\n- Flag `tengu_rosy_puddle`: Not enough to say (read for one account on one subscription tier against v2.1.311; this account: no value returned, anonymous baseline: no value returned, compiled default: on) 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: Settings\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}