Follow Discord
Sweep 10 Nov 2026 · 02:18Z Build v2.1.322 539 read Stable v2.1.311 Latest v2.1.322 Next v2.1.322 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.268 ·

Plugin manager waits for pending toggles and clarifies when changes apply

The plugin manager now waits for enable/disable actions to finish and tells you if changes apply immediately or need a reload

Group of 3 You'll notice No documentation found Internal Changes
JSON All of v2.1.268
You'll noticeTier: 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.268,
ImprovementsSection of the release

What

  • Closing the plugin manager menu after toggling plugins used to show a static reminder message immediately. Now it tracks in-flight enable/disable promises and, if any are still pending, waits for all of them to settle before returning to the menu, instead of firing the reminder text before the toggle finished.
  • The reminder text is now conditional on a new changesApplyOnClose flag: when set, plugin-enable confirmations say the change applies as soon as the menu closes; otherwise they still tell you to run /reload-plugins.
  • The installed-plugins management screen now receives this changesApplyOnClose prop, wired to the same "needs refresh" state used for the reload prompt.

Why This avoids showing a misleading confirmation before a plugin toggle has actually finished, and makes clear whether you need to run /reload-plugins or the change already took effect.

Read from
Names in the bundlechangesApplyOnClose

See this entry in the whole of v2.1.268 →

Feedback