{"version":"2.1.300","anchor":"cold-start-plugin-policy-waits-for-pending-answer","canonical_anchor":"cold-start-plugin-policy-waits-for-pending-answer","heading":"Plugin policy at startup now waits for a pending answer first","tier":"internal","area":"Plugins","scope":"org","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300\/e\/cold-start-plugin-policy-waits-for-pending-answer","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300","markdown":"### Plugin policy at startup now waits for a pending answer first\n\nWhen Claude Code first starts, its plugin policy check now waits if an answer is still pending before it checks remote managed settings\n\n**What**\n\nWhen Claude Code first starts, it works out which plugins are allowed. If a check at that point reports its answer as \"unanswered\", Claude Code now waits for that answer before it moves on to the remote managed-settings check. Managed settings are settings your organization controls. Previously it went straight to the remote managed-settings check.\n\n**Why**\n\nThis changes the order of steps at startup when managed settings are involved.\n\n- Area: Plugins\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: org\n- Heads-up: no"}