{"version":"2.1.287","anchor":"plugin-not-found-error-visibility-and-marketplace-autoupdate","canonical_anchor":"plugin-not-found-error-visibility-and-marketplace-autoupdate","heading":"Missing-plugin errors account for removed plugins and an unreadable installed_plugins.json","tier":"notice","area":"Plugins","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287\/e\/plugin-not-found-error-visibility-and-marketplace-autoupdate","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287","markdown":"### Missing-plugin errors account for removed plugins and an unreadable installed_plugins.json\n\nPlugin-not-found errors are hidden for plugins removed from the directory, and an unreadable installed_plugins.json is now named as the cause\n\n**Unclear.** It is not clear which kinds of marketplace source are skipped by the auto-update sync.\n\n**What**\n\nClaude Code reports more accurately why a plugin (an add-on that extends Claude Code) is missing.\n\n- A `plugin-not-found` error is no longer shown for a plugin marked `removedFromDirectory`, unless `registryReadFailed` is also true.\n\n- When the plugin registry could not be read, the message now says the plugin is not loaded because `installed_plugins.json` could not be read, so its install could not be checked. Before, it said only `Plugin \"...\" not cached at ...`.\n\n- Separately, when the `autoUpdate` setting is copied from your settings to plugin marketplaces, some marketplaces are now skipped based on their source.\n\n**Why**\n\nYou stop seeing old not-found errors for plugins that were deliberately removed from the directory. When a plugin really is missing because its install record could not be read, the message points at `installed_plugins.json` instead of reporting a plain cache miss.\n\n- Area: Plugins\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}