{"version":"2.1.239","anchor":"plugin-errors-now-say-what-to-do-based-on-where-the-plugin-c","canonical_anchor":"plugin-errors-now-say-what-to-do-based-on-where-the-plugin-c","heading":"Plugin errors now say what to do based on where the plugin came from","tier":"notice","area":"Plugins","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239\/e\/plugin-errors-now-say-what-to-do-based-on-where-the-plugin-c","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239","markdown":"### Plugin errors now say what to do based on where the plugin came from\n\nPlugin load errors now give advice matched to how the plugin was installed, including synced copies being shadowed.\n\n**What**\n\nWhen a plugin does not load, the advice you get depends on how it was installed: passed with `--plugin-dir`, picked up from a skills directory, or synced from claude.ai. Shadowed synced plugins get their own named warning explaining that the local copy of the same name takes precedence.\n\n**Details**\n\n- Plugin sources gained readable labels, including \"plugins synced from your claude.ai account\".\n- The `pluginRoot` field in a marketplace definition now has a much fuller schema description.\n\n**Evidence**\n\n`on this machine has the same name and takes precedence`\n\n- Area: Plugins\n- Names: `--plugin-dir`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}