{"version":"2.1.284","anchor":"plugin-manifest-parsevalidation-errors-name-the-manifest-fi","canonical_anchor":"plugin-manifest-parsevalidation-errors-name-the-manifest-fi","heading":"Plugin manifest errors now say which manifest file is broken","tier":"notice","area":"Plugins","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.284\/e\/plugin-manifest-parsevalidation-errors-name-the-manifest-fi","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.284","markdown":"### Plugin manifest errors now say which manifest file is broken\n\nPlugin manifest parse and validation errors now end with the path of the manifest file, and are cut short later than before\n\n**What**\n\nA plugin's manifest is the file that describes the plugin to Claude Code. When a manifest cannot be read (\"Manifest parse error\") or does not pass its checks (\"Manifest validation failed\"), the error now ends with \"(in )\", naming the file. Before, the path was not included.\n\nThese messages are also allowed to run longer before being cut short, up to 500 or 1000 characters.\n\n**Why**\n\nIf a plugin fails to load, you can go straight to the file that needs fixing.\n\n- Area: Plugins\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}