Command-built plugins refresh on their own background schedule, and block if the command changed.
tengu_plugin_command_source_refresh Not enough to sayNothing here resolved what this flag was doing on this version, so nothing here should be read as on or off.
This account: no value returned · anonymous baseline: no value returned · compiled default in v2.1.229: off
These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.
Read once, for one account on one subscription tier, against v2.1.229. It isn't a statement about your account. What a flag value here can and cannot tell you
What's wrong with this entry?
Plugins installed by running a command are now left out of the normal plugin autoupdate pass and refreshed by a separate background job that re-runs the command you accepted. If the marketplace's command no longer matches the one you consented to, the refresh blocks with an explanation instead of running it. On by default via tengu_plugin_command_source_refresh; managed settings can also disable it, in which case those plugins are simply skipped.
- the autoupdate telemetry event now carries
command_plugins_refreshedandcommand_plugin_refresh_failedcounts
Plugin autoupdate: command-source refresh disabled by tengu_plugin_command_source_refresh (still excluding command-sourced plugins from the regular pass), Plugin autoupdate: skipped (auto-updater disabled)
Strings lifted out of the shipped bundle, so the claim above can be checked against them.