{"version":"2.1.304","anchor":"policy-limits-cache-requires-a-server-attributable-principal","canonical_anchor":"policy-limits-cache-requires-a-server-attributable-principal","heading":"Policy limit results are saved to disk only for some sign-in credentials","tier":"internal","area":"Managed Settings","scope":"org","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304\/e\/policy-limits-cache-requires-a-server-attributable-principal","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304","markdown":"### Policy limit results are saved to disk only for some sign-in credentials\n\nPolicy limit results are now saved to disk only when the server can tie the credential to an account; otherwise they last for the session only\n\n**Unclear.** Which kinds of sign-in credentials count as server-attributable is not known.\n\n**What**\n\nClaude Code checks policy limits, which are restrictions an organization can place on usage, and can save the result to disk so it does not have to ask again. It now saves that result only when the credential in use can be tied to an account on the server side. Before, the check was looser.\n\nFor any other credential, Claude Code uses the result for the current session and does not save it. It reports this with a message that says there is \"no server-attributable principal for this credential\".\n\n**Why**\n\nSome credentials no longer have their policy results stored on disk. With those credentials the check runs again in each new session rather than reusing a saved answer.\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"}