{"version":"2.1.284","anchor":"promo-credit-status-cache-gets-a-configurable-max-age","canonical_anchor":"promo-credit-status-cache-gets-a-configurable-max-age","heading":"Promo eligibility status is cached on disk with a configurable max age","tier":"internal","area":"Usage & Limits","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.284\/e\/promo-credit-status-cache-gets-a-configurable-max-age","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.284","markdown":"### Promo eligibility status is cached on disk with a configurable max age\n\nPromo eligibility is now saved per account and endpoint and reused for up to an hour, with a new statusMaxAgeSeconds setting controlling the age\n\n**What**\n\nWhen Claude Code starts, it may check whether your account is eligible for a promotional credit and whether you have already claimed it. That answer used to be kept only in memory for the running program, so every startup asked the server again. Now:\n\n- `promoStartupStatusCache` saves the eligible and claimed status in the global config file, separately for each account and each server address (endpoint).\n\n- The saved answer is reused for up to 3600 seconds (one hour) instead of asking the server on every startup.\n\n- The status is asked again after `\/clear`, the command that starts a new conversation.\n\n- The promo claim config gains `statusMaxAgeSeconds` (minimum 0, default 3600), which is passed as `maxAgeSeconds` to the status request.\n\n- When `statusMaxAgeSeconds` is not zero, the local cache is no longer rewritten from the fetched status. Before, it was updated whenever the eligible or claimed value differed.\n\n**Why**\n\nIn practice Claude Code makes fewer network requests about promotions when it starts. If a promo's status changes on the server, it can take up to the configured max age before a new startup notices.\n\n- Area: Usage & Limits\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5"}