{"version":"2.1.307","anchor":"policy-banner-adds-restrictionsonly-state","canonical_anchor":"policy-banner-adds-restrictionsonly-state","heading":"Policy status shows when cached restrictions still apply after a failed fetch","tier":"notice","area":"Managed Settings","scope":"org","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.307\/e\/policy-banner-adds-restrictionsonly-state","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.307","markdown":"### Policy status shows when cached restrictions still apply after a failed fetch\n\nWhen fetching remote policy settings fails but a cached copy exists, the status now says the cached policy's restrictions still apply\n\n**What**\n\nOrganizations can push settings to Claude Code from a server, known as remote settings or remote policy. When fetching them fails and a saved (cached) copy exists, the failure state can now carry `restrictionsOnly: true`.\n\nWhen that state is set, the policy status line ends with \"\u00b7 the cached policy's restrictions still apply\". Before, this situation showed \"\u00b7 no remote policy applied\".\n\n**Why**\n\nThe old wording suggested no policy was in force when the cached restrictions were in fact still in force. If you work under managed settings, the status now tells you that those limits remain even though the latest copy could not be fetched.\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"}