{"version":"2.1.299","anchor":"policy-limits-cache-gated-by-signed-copy-trust-at-rest","canonical_anchor":"policy-limits-cache-gated-by-signed-copy-trust-at-rest","heading":"Saved organisation policy limits are used only if their signed copy checks out","tier":"notice","area":"Managed Settings","scope":"org","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299\/e\/policy-limits-cache-gated-by-signed-copy-trust-at-rest","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299","markdown":"### Saved organisation policy limits are used only if their signed copy checks out\n\nClaude Code now uses its saved copy of policy limits only when a signed copy verifies against the organisation; otherwise it starts without it\n\n**Unclear.** It is not known whether this stricter check is switched on for everyone or held behind a remote switch.\n\n**What**\n\nPolicy limits are restrictions an organisation places on Claude Code, and Claude Code keeps a saved copy of them on disk. Until now a signed copy of that saved data was only checked in the background. The check did not decide anything, and the saved copy was used whenever its stamp matched.\n\nNow the saved copy is trusted only if its signed copy verifies against the organisation the administrator pinned. If it does not verify, Claude Code starts as if nothing were saved. Compliance restrictions and explicit denials still apply in that case. Claude Code also records whether the stored copy was trusted, and records when the signed identity behind the cache changes.\n\n**Why**\n\nIn organisations with managed settings, Claude Code may refuse a saved policy cache after an upgrade and fetch the limits afresh, which can show up as a slower or different start.\n\n- Area: Managed Settings\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: org\n- Heads-up: no"}