Follow Discord
Sweep 22 Oct 2026 · 21:04Z Build v2.1.309 528 read Stable v2.1.308 Latest v2.1.309 Next v2.1.309 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.300 ·

Plugin auto-update log now says when it is waiting for organization settings

When plugin auto-update holds back a refresh, its log now says if it is waiting for organization settings rather than blocked by them

Under the hood Internal Changes
JSON All of v2.1.300
Under the hoodTier: how much it should matter to you
1Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
PluginsArea: what it touches
Internal ChangesKind: in v2.1.300,
Internal ChangesSection of the release
What

Plugins can update themselves automatically, and part of that is refreshing the commands they provide. Organization policy can hold this refresh back.

The log line used to say the refresh was disabled by managed settings in every case. It now separates two cases:

  • Disabled by the organization's managed settings.
  • Held because the organization's settings have not been read yet.
Why

The 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.

Read from
Feature flag
tengu_plugin_command_source_refresh Not enough to say

Nothing 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.300: 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.

Read once, for one account on one subscription tier, against v2.1.300. It isn't a statement about your account. What a flag value here can and cannot tell you

See this entry in the whole of v2.1.300 →

Feedback