Plugin reload banner is dismissed instead of getting stuck

The "reload plugins" banner now goes away on its own instead of sticking around.

You'll notice Bug Fixes

JSON All of v2.1.221

You'll noticeTier: how much it should matter to you

3Useful: my rating, 1 to 5

0Signal: worth watching, 1 to 5

PluginsArea: what it touches

Bug FixesKind: in v2.1.221, 03 Aug 26

Bug FixesSection of the release

What

The prompt to reload plugins now clears once it no longer applies.

Details

the plugin-changed effect explicitly dismisses the plugin-reload-pending notification when the condition clears, rather than returning early and leaving the banner on screen
plugin list and detail keyboard navigation is suppressed while a reload is in flight

Evidence

Plugins changed. Run /reload-plugins to activate.

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

How sure we are

One source agreesOne thing we can check says the same as this entry.

Anthropic's release notes agreeFixed the "Plugins changed" notification lingering after plugins were reloaded instead of clearing

See this entry in the whole of v2.1.221 →

The build it came inv2.1.221

3 Aug 2026 · 308 entries, this one is #179.

Use it now28
You'll notice152
Nothing to try yet44
Under the hood84

Either side of it

v2.1.220Older
v2.1.222Newer

Open the release →

Names in this entry

slash/reload-plugins
Reload all active plugins to apply pending changes without restarting. Reports counts for each reloaded component and flags any load errors. When the reload would change which MCP tools are loaded and invalidate the prompt cache, the command warns and skips unless you pass --force. Also available in non-interactive mode (-p), the Agent SDK, and the desktop app, where it runs only on input typed directly into the session and doesn't apply plugin MCP server changes; requires Claude Code v2.1.260 or later. See Apply plugin changes without restarting

Anthropic's notes

Upstream's own release notes for v2.1.221 name something this entry names, so the two are probably about the same change. Probably: the pairing is made on a shared name rather than on the words around it.

Fixed the "Plugins changed" notification lingering after plugins were reloaded instead of clearing
Changed plugins installed from /plugin to activate immediately when safe, instead of always requiring /reload-plugins

Is this right?