{"version":"2.1.300","anchor":"plugin-command-source-refresh-message-distinguishes-waiting","canonical_anchor":"plugin-command-source-refresh-message-distinguishes-waiting","heading":"Plugin auto-update log now says when it is waiting for organization settings","tier":"internal","area":"Plugins","scope":"org","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300\/e\/plugin-command-source-refresh-message-distinguishes-waiting","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300","markdown":"### Plugin auto-update log now says when it is waiting for organization settings\n\nWhen plugin auto-update holds back a refresh, its log now says if it is waiting for organization settings rather than blocked by them\n\n**What**\n\nPlugins can update themselves automatically, and part of that is refreshing the commands they provide. Organization policy can hold this refresh back.\n\nThe log line used to say the refresh was disabled by managed settings in every case. It now separates two cases:\n\n- Disabled by the organization's managed settings.\n\n- Held because the organization's settings have not been read yet.\n\n**Why**\n\nThe new wording suggests that, while the organization's policy is still unknown, the refresh is postponed rather than turned off. That helps when reading logs to work out why plugin commands did not refresh.\n\n- Flag `tengu_plugin_command_source_refresh`: Not enough to say (read for one account on one subscription tier against v2.1.300; this account: no value returned, anonymous baseline: no value returned, compiled default: on) 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.\n- Area: Plugins\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: org\n- Heads-up: no"}