{"version":"2.1.305","anchor":"plugin-sync-absence-diagnostics-and-manifest-containment-hin","canonical_anchor":"plugin-sync-absence-diagnostics-and-manifest-containment-hin","heading":"A synced plugin that cannot be found now comes with a reason","tier":"notice","area":"Plugins","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.305\/e\/plugin-sync-absence-diagnostics-and-manifest-containment-hin","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.305","markdown":"### A synced plugin that cannot be found now comes with a reason\n\nWhen a synced plugin is missing, the error now says why, and the manifest fix hint explains symlink and outside-folder refusals\n\n**What**\n\nWhen Claude Code looks for a synced plugin and cannot find it, the error now carries a reason. Examples include:\n\n- the plugin was held back\n\n- a local copy took priority\n\n- the plugin was not in the listing\n\nThe hint shown when a plugin manifest (the file describing the plugin) fails validation has also changed. It used to say only to check that the file follows the required schema. It now explains that a manifest is read only when it is confirmed to be inside the plugin's own folder, which covers refusals caused by symbolic links (shortcuts to files elsewhere).\n\n**Why**\n\nPlugin sync failures are easier to work out, since the message now says why a plugin is missing or why its manifest was refused.\n\n- Area: Plugins\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}