{"version":"2.1.261","anchor":"claudeai-flag-lets-you-add-a-claudeai-hosted-plugin-mar","canonical_anchor":"claudeai-flag-lets-you-add-a-claudeai-hosted-plugin-mar","heading":"Support for claude.ai-hosted plugin marketplaces","tier":"use","area":"Plugin Marketplace","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.261\/e\/claudeai-flag-lets-you-add-a-claudeai-hosted-plugin-mar","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.261","markdown":"### Support for claude.ai-hosted plugin marketplaces\n\nYou can now add a claude.ai-hosted plugin marketplace with a new --claudeai flag.\n\nA new `plugin marketplace add --claudeai <name>` option is wired end-to-end: a `claudeai` plugin\/marketplace `source` kind is now accepted throughout install\/eligibility\/hostPattern checks alongside `github`\/`git`\/`url`, catalog files for it are stored under a `.marketplace-<id>.json` naming scheme, and adding a marketplace whose name starts with the reserved claude.ai prefix without `--claudeai` is now explicitly refused. Installed plugins from this source also get new fields recorded: `claudeaiPluginId` and `archiveSha256`.\n\nNew helper functions `gl`, `gUe`, and `hUe` let marketplace\/plugin lookups fall back to a locally-synced 'claude.ai marketplace registry' file (read via `RF()`) whenever the normal `known_marketplaces.json`-derived cache lookup misses or the cache file is unreadable (ENOENT). Previously these lookups just returned null on a cache miss; now they resolve entries against the registry and, for plugins, can synthesize a `claudeai`-sourced plugin entry from account plugin data (`Ap().plugins`).\n\n- Area: Plugin Marketplace\n- Names: `--claudeai`, `--sparse`, `--scope`\n- Tier: Use it now\n- Useful: 5\/5\n- Signal: 2\/5"}