{"version":"2.1.287","anchor":"built-in-plugin-directory-marketplace-add-remove-list-and","canonical_anchor":"built-in-plugin-directory-marketplace-add-remove-list-and","heading":"Plugin commands now handle the built-in directory marketplace","tier":"use","area":"Plugins","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287\/e\/built-in-plugin-directory-marketplace-add-remove-list-and","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287","markdown":"### Plugin commands now handle the built-in directory marketplace\n\nPlugin marketplace add, remove, list, details and \/reload-plugins now treat the built-in plugin directory specially, including when policy blocks it\n\n**Unclear.** It is not clear what makes the built-in directory unavailable rather than on, so it is not known who sees these messages.\n\n**What**\n\nClaude Code comes with a built-in plugin directory marketplace, which is a catalog of plugins you can install. The plugin commands now recognise it and handle it on its own terms instead of treating it like any other marketplace:\n\n- `claude plugin marketplace add` now recognises the built-in directory. If your organization's policy blocks it, the command says it \"is blocked by your organization\". It rejects `--sparse` and `--scope` for this marketplace, with the message \"is built in and not declared in any settings scope. Omit --sparse and --scope to turn it on.\" If the marketplace is turned off, `add` turns it back on.\n\n- `remove` turns the built-in directory off but keeps the plugins you already installed from it.\n\n- `list` shows the built-in directory as built in and off when it is turned off, with a \"Turn it back on\" line.\n\n- `\/reload-plugins` adds a note that the directory \"could not be reached, so its plugins were not loaded\" when the directory is unreachable.\n\n- `claude plugin details` now gives specific reasons when a plugin from the built-in directory is unavailable: it is blocked by policy (`policy_blocked`), or the directory's catalog is missing (`directory_catalog_missing`). Before, it always reported a generic \"not found\".\n\nBefore this release, `add` only had an error about the name being reserved, and `remove` handled the built-in directory the same way as other marketplaces.\n\n**Why**\n\nWhen a plugin from the built-in directory is not available, the messages now say why: your organization blocked it, the directory could not be reached, or its catalog is missing. You can also turn the built-in directory off without losing installed plugins, and turn it back on with `add`.\n\n- Area: Plugins\n- Tier: Use it now\n- Useful: 4\/5\n- Signal: 2\/5"}