{"version":"2.1.323","anchor":"policy-limits-cold-hosted-process-holds-off-the-stored-poli","canonical_anchor":"policy-limits-cold-hosted-process-holds-off-the-stored-poli","heading":"Freshly started hosted sessions wait before trusting a saved policy file","tier":"notice","area":"Managed Settings","scope":"org","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/policy-limits-cold-hosted-process-holds-off-the-stored-poli","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### Freshly started hosted sessions wait before trusting a saved policy file\n\nA hosted Claude Code process that starts cold now waits for its own policy fetch before adopting the saved policy file, though its denials still apply\n\n**What**\n\nOrganizations can set policy limits that control what Claude Code may do, and Claude Code keeps a saved copy of them in a file. When Claude Code runs as a hosted process that has just started from scratch (a cold start), it no longer adopts that saved file right away. It waits until its own request for the current policy gets an answer.\n\nAnything the saved file denies still applies during the wait. Claude Code writes a log line explaining that it is holding off.\n\n**Why**\n\nThis closes a window in which an outdated saved policy could be trusted before the current one arrived.\n\n- Area: Managed Settings\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: org\n- Heads-up: no"}