{"version":"2.1.283","anchor":"plugin-load-errors-now-include-the-path-and-manifest-name","canonical_anchor":"plugin-load-errors-now-include-the-path-and-manifest-name","heading":"Plugin load errors now include the plugin's folder path and name","tier":"notice","area":"Plugins","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283\/e\/plugin-load-errors-now-include-the-path-and-manifest-name","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283","markdown":"### Plugin load errors now include the plugin's folder path and name\n\nWhen a plugin fails to load, its error record now includes the plugin's path and manifest name where Claude Code knows them\n\n**Unclear.** Whether any screen, such as `\/plugin` or `claude doctor`, displays the new fields is not settled.\n\n**What**\n\nPlugins are add-on packages that extend Claude Code. When one fails to load with a general error, the error record now includes the path to the plugin and the name from its manifest (the file that describes the plugin), when those are known. Before, the record held only the error type, where the plugin came from, and the error message.\n\n**Why**\n\nWith a path and a name attached, a broken plugin should be easier to track down among several installed ones.\n\n- Area: Plugins\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}