{"version":"2.1.287","anchor":"plugin-directory-search-and-marketplace-code-added-with-an-o","canonical_anchor":"plugin-directory-search-and-marketplace-code-added-with-an-o","heading":"Anthropic Directory plugin marketplace with search, policy controls and stricter install checks","tier":"notice","area":"Plugins","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287\/e\/plugin-directory-search-and-marketplace-code-added-with-an-o","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287","markdown":"### Anthropic Directory plugin marketplace with search, policy controls and stricter install checks\n\nA built-in Anthropic Directory marketplace adds plugin search, org and managed-settings controls, and stricter checks with new error codes on update and uninstall\n\n**Unclear.** It is not known what starts the search or the marketplace, or what the built-in default for the marketplace is.\n\n**What**\n\nA plugin marketplace is a source you install plugins from. Claude Code adds a built-in one, the Anthropic Directory, built from the public plugin directory:\n\n- Catalogue: listings are fetched from `\/api\/directory\/plugins` and cached in `plugin-directory-cache-v2.json`. A listing is used only if it is pinned to a reviewed commit (`reviewed_commit`) and has a valid repository address. Otherwise it is skipped as `no_pin`, `bad_url`, `bad_path` or `other_surface`.\n\n- On or off: your choice is stored in `plugin-directory-marketplace.json`. Where that file does not exist, the default could not be traced.\n\n- Search: refused when the organisation policy `allow_plugin_directory_search` does not allow it, or when only essential traffic is allowed. The `\/plugin` subcommands `directory` and `search` open a directory view with your query when a feature check passes, and otherwise open the plugin menu as before.\n\n- Admin controls: managed settings can turn the directory off with `disablePluginDirectory`. Policy lists gain a `pluginDirectory` entry standing for this marketplace. Under `strictKnownMarketplaces`, any allowlist blocks it unless it is listed, and under `blockedMarketplaces` it can be blocked on its own.\n\n- Update and uninstall: both check the directory more strictly and can fail with `directory_binding_unreadable`, `directory_identity_changed`, `directory_listing_not_installable`, `plugin_policy_blocked`, `directory_unavailable`, `dependencies_not_installed` or `dependencies_not_screened`. Before, the only message was \"Plugin not found in marketplace\".\n\n- Uninstall refuses to run in a workspace you have not trusted and checks that the plugin is no longer enabled in your settings.\n\n- A plugin removed from the directory gets a specific \"not loaded\" message.\n\n- An update can also install the packages a plugin lists.\n\n- The `plugin:cycleMarketplace` keyboard action is now accepted, and the marketplace list falls back to a default label for the default marketplace.\n\nWhere this code is called from was not found in every part of the release examined.\n\n**Why**\n\nThis is a new place to find plugins, with directory plugins tied to the reviewed repository they came from. Administrators can allow, block or switch it off, and failed updates or uninstalls now say why.\n\n- Area: Plugins\n- Names: `allow_plugin_directory_search`\n- Tier: You'll notice\n- Useful: 4\/5\n- Signal: 3\/5"}