{"version":"2.1.229","anchor":"plugins-can-be-installed-from-a-command-that-produces-the-pl","canonical_anchor":"plugins-can-be-installed-from-a-command-that-produces-the-pl","heading":"Plugins can be installed from a command that produces the plugin directory","tier":"use","area":"Plugins","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.229\/e\/plugins-can-be-installed-from-a-command-that-produces-the-pl","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.229","markdown":"### Plugins can be installed from a command that produces the plugin directory\n\nMarketplaces can declare command plugin sources, and admins can block them with one setting.\n\n**What**\n\nA marketplace can now declare a `command` plugin source, where Claude Code runs that command on your machine to produce the plugin directory. Installs and updates prompt before running the command. A new managed setting `disableCommandPluginSources` turns it off; when it is unset, the existing `allowManagedHooksOnly` managed setting decides, and an invalid value for either key is treated as disabled.\n\n**Details**\n\n- `command` is now listed alongside github, git-subdir, npm, url and archive in marketplace validation messages.\n- Each installation records the command that produced it, the directory it produced, and the directories previous runs produced, so the sandbox keeps refusing writes to superseded producer directories.\n- Both settings keys are read from managed settings only, so a user or project settings file cannot re-enable this.\n\n**Evidence**\n\n`disableCommandPluginSources`\n\n- Area: Plugins\n- Names: `disableCommandPluginSources`, `allowManagedHooksOnly`\n- Tier: Use it now\n- Useful: 3\/5\n- Signal: 3\/5"}