{"version":"2.1.277","anchor":"settings-sync-invalidation-now-includes-a-policy-verdict-tri","canonical_anchor":"settings-sync-invalidation-now-includes-a-policy-verdict-tri","heading":"Settings-sync invalidation now includes a policy_verdict trigger","tier":"internal","area":"Settings","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.277\/e\/settings-sync-invalidation-now-includes-a-policy-verdict-tri","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.277","markdown":"### Settings-sync invalidation now includes a policy_verdict trigger\n\nSettings and hooks can now be invalidated by a new policy_verdict trigger\n\n**What**\n\nThe list of reasons that can cause Claude Code to invalidate and reload its settings and hooks now includes a new `policy_verdict` entry, alongside the existing `settings_sync`, `account_change`, and `hooks_invalidate` reasons.\n\n**Why**\n\nThis lets a policy decision (such as one made by an organization's admin controls) trigger a refresh of settings and hooks, so changes driven by policy take effect without needing one of the other existing triggers.\n\n- Area: Settings\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}