{"version":"2.1.287","anchor":"plugin-not-found-errors-now-explain-removal-from-the-marke","canonical_anchor":"plugin-not-found-errors-now-explain-removal-from-the-marke","heading":"Plugin errors explain when a plugin was removed from its marketplace directory","tier":"notice","area":"Plugins","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287\/e\/plugin-not-found-errors-now-explain-removal-from-the-marke","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287","markdown":"### Plugin errors explain when a plugin was removed from its marketplace directory\n\nWhen a plugin is gone from its marketplace directory, the error now says so and suggests a fix that fits the case\n\n**Unclear.** What makes Claude Code decide a plugin was removed from the directory, and whether that is behind a switch, was not stated.\n\n**What**\n\nBefore, a missing plugin produced a general \"not found in marketplace\" error with the hint \"Plugin may not exist in marketplace\". When a plugin has been removed from its marketplace directory, the error now says so, and the suggested fix depends on why:\n\n- The listing was renamed: uninstall the plugin, then install it under its new name from `\/plugin` \u2192 Discover.\n\n- The listing can no longer be installed.\n\n- The plugin's identity changed.\n\n- The plugin registry could not be read: run `\/reload-plugins`, and if the plugin still does not load, fix or restore `installed_plugins.json` in the plugins directory.\n\nErrors for a marketplace that failed to load and for a plugin blocked by policy also get messages specific to the directory. An error for a plugin missing from the local cache now points to `installed_plugins.json`.\n\n**Why**\n\nIf a plugin you use was delisted or renamed, you now get steps you can follow instead of a general not-found message.\n\n- Area: Plugins\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}