{"version":"2.1.300","anchor":"plugin-command-and-headershelper-sources-held-until-the-orga","canonical_anchor":"plugin-command-and-headershelper-sources-held-until-the-orga","heading":"Plugin commands wait until your organization's settings are read","tier":"notice","area":"Plugins","scope":"both","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300\/e\/plugin-command-and-headershelper-sources-held-until-the-orga","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300","markdown":"### Plugin commands wait until your organization's settings are read\n\nPlugin command sources and marketplace `headersHelper` commands no longer run in a tool server and wait until organization settings have loaded\n\n**What**\n\nPlugins add features to Claude Code, and a marketplace is a catalog you install them from. Some plugins come from a source that runs a command, and a marketplace can set a `headersHelper` command that produces extra request headers. These commands now have new limits:\n\n- They refuse to run in a tool server, a background service that provides tools. The message is \"A tool server doesn't run a plugin's command on its own.\"\n\n- They are held until your organization's managed settings have been read, and Claude Code waits for that answer\n\nBefore, only the managed policy setting `disableCommandPluginSources` applied. The message about organization settings now also differs depending on whether those settings exempt a `headersHelper`.\n\n**Why**\n\nIn organizations, these commands do not run before Claude Code knows whether they are allowed. The plugin or marketplace is not fetched until the organization's settings load.\n\n- Area: Plugins\n- Names: `headersHelper`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: both\n- Heads-up: yes"}