{"version":"2.1.229","anchor":"command-sourced-plugins-are-not-rebuilt-behind-your-back","canonical_anchor":"command-sourced-plugins-are-not-rebuilt-behind-your-back","heading":"Command-sourced plugins are not rebuilt behind your back","tier":"notice","area":"Plugins","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.229\/e\/command-sourced-plugins-are-not-rebuilt-behind-your-back","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.229","markdown":"### Command-sourced plugins are not rebuilt behind your back\n\nPlugins that build via a command won't silently run it; you get an error telling you to update.\n\n**What**\n\nWhen a plugin installed from a command has no cached copy, Claude Code will not run its command if the plugin is disabled or if background command execution is turned off. Instead it shows a load error telling you to run `claude plugin update` in a terminal.\n\n**Details**\n\n- The refusal is reported as `command_source_inactive` rather than a generic operation failure.\n\n**Usage**\n\n`claude plugin update` **Evidence** `command_source_inactive`\n\n- Area: Plugins\n- Names: `claude plugin update`\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5"}