{"version":"2.1.292","anchor":"plugin-commands-wait-for-remote-managed-settings-before-runn","canonical_anchor":"plugin-commands-wait-for-remote-managed-settings-before-runn","heading":"Plugin commands wait for your organization's managed settings","tier":"notice","area":"Plugins","scope":"both","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.292\/e\/plugin-commands-wait-for-remote-managed-settings-before-runn","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.292","markdown":"### Plugin commands wait for your organization's managed settings\n\nMost claude plugin commands now wait for remote managed settings to load and do not run if those settings are not approved\n\n**Unclear.** It is not clear in which situations Claude Code waits, so it is unknown whether every reader is affected.\n\n**What**\n\nManaged settings are settings an organization's administrator sets centrally for everyone. Most `claude plugin` commands now wait until these settings have loaded from the server. If the settings are not approved, or Claude Code is shutting down, the command does not run.\n\nThese commands do not wait:\n\n- `claude plugin list`\n\n- `claude plugin marketplace list`\n\n- `claude plugin validate`\n\n- `claude plugin tag`\n\n- `claude plugin test`\n\n- `claude plugin eval init`\n\n**Why**\n\nIn an organization that manages plugin policy, people can no longer install or change plugins before that policy has been confirmed.\n\n- Area: Plugins\n- Names: `claude plugin`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: both\n- Heads-up: yes"}