{"version":"2.1.284","anchor":"invalid-plugin-manifests-reported-as-specific-errors","canonical_anchor":"invalid-plugin-manifests-reported-as-specific-errors","heading":"Plugin load errors now say exactly what is wrong with the manifest","tier":"notice","area":"Plugins","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.284\/e\/invalid-plugin-manifests-reported-as-specific-errors","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.284","markdown":"### Plugin load errors now say exactly what is wrong with the manifest\n\nA plugin that fails to load because of its manifest now shows whether the file could not be read or which checks it failed\n\n**What**\n\nA plugin's manifest is the file that describes the plugin to Claude Code. When a plugin fails to load because of this file, the error now says which kind of problem it was, instead of being a generic error:\n\n- The file could not be read at all: the error includes what went wrong while reading it.\n\n- The file was read but broke the rules: the error names the manifest's path and lists the problems. If there are many, it shows the first few and adds \"and N more\".\n\n**Why**\n\nThe plugin error views, such as the one in `\/plugin`, can point you at the exact problem in the manifest. You no longer have to guess from a general failure message.\n\n- Area: Plugins\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}