{"version":"2.1.319","anchor":"synced-plugin-shadow-warning-has-a-distinct-hint-for-inline","canonical_anchor":"synced-plugin-shadow-warning-has-a-distinct-hint-for-inline","heading":"Better advice when an inline plugin hides a claude.ai plugin","tier":"notice","area":"Plugins","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319\/e\/synced-plugin-shadow-warning-has-a-distinct-hint-for-inline","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319","markdown":"### Better advice when an inline plugin hides a claude.ai plugin\n\nWhen an inline plugin hides a synced claude.ai plugin, the warning now says to disable or remove it instead of pointing to \/plugin\n\n**What**\n\nPlugins add commands and other features to Claude Code. Plugins you set up on claude.ai can sync to Claude Code, and another plugin with the same name can hide, or shadow, the synced one. Claude Code warns you when that happens.\n\nWhen the plugin doing the hiding is an inline plugin, the warning now tells you to disable or remove it to use the claude.ai copy instead. It no longer suggests running a plugin enable command or using `\/plugin`. Other cases keep the old advice.\n\n**Why**\n\nInline plugins cannot be enabled through `\/plugin`, so the old advice sent people to a step that did not help.\n\n- Area: Plugins\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}