{"version":"2.1.323","anchor":"policy-limits-cache-falls-back-to-a-fresh-state-instead-of-n","canonical_anchor":"policy-limits-cache-falls-back-to-a-fresh-state-instead-of-n","heading":"Policy limits fall back to a fresh default when the saved copy can't be used","tier":"internal","area":"Managed Settings","scope":"org","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/policy-limits-cache-falls-back-to-a-fresh-state-instead-of-n","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### Policy limits fall back to a fresh default when the saved copy can't be used\n\nIf the saved policy limits can't be used, Claude Code now builds a fresh default state instead of having no policy answer at all\n\n**Unclear.** What the freshly built state contains, and so which limits apply when the saved copy is unusable, is not stated.\n\n**What**\n\nClaude Code keeps a saved copy, called a cache, of its policy limits information. Sometimes that saved copy can't be used, in any of these cases:\n\n- The cache is refused.\n\n- The cache can't be read.\n\n- The cache fails the check that decides whether it may be used.\n\nIn those cases, loading policy limits used to produce nothing. It now produces a freshly built state.\n\n**Why**\n\nWhen Claude Code starts without a usable saved copy, it now has a default policy answer to work from instead of none.\n\n- Area: Managed Settings\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: org\n- Heads-up: no"}