Claude Code v2.1.221 · 3 Aug 2026
/plugin reload checks prompt-cache impact
Activating plugins from the /plugin dialog now warns you before it invalidates your conversation's prompt cache.
You'll notice Tier: how much it should matter to you
3 Useful: my rating, 1 to 5
0 Signal: worth watching, 1 to 5
Plugins Area: what it touches
Improvements Kind: in v2.1.221, 03 Aug 26
Improvements Section of the release
What
Activating plugins from the plugin management dialog now goes through the same prompt-cache check that /reload-plugins uses, so an install does not silently invalidate the conversation's prompt cache.
Details
The dialog is passed getReloadCacheImpactOptions, carrying the model plus dynamic MCP config. An install-triggered activation can now bail out with a cache_impact outcome. The equivalent /reload-plugins warning text already existed. Evidence
getReloadCacheImpactOptions
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
How sure we are
One source agrees One thing we can check says the same as this entry.
Anthropic's release notes agree Changed /plugin install to refresh a stale marketplace catalog and retry before reporting a plugin not found
See this entry in the whole of v2.1.221 →
3 Aug 2026 · 308 entries, this one is #119.
Use it now28 You'll notice152 Nothing to try yet44 Under the hood84
Open the release →
Names in this entry
slash /plugin Manage Claude Code plugins . Run with no argument to open the plugin menu, or pass a subcommand such as list, install, enable, or disable to act directly. Claude Code can activate a plugin during the install; the install summary tells you whether it did or whether to run /reload-plugins
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.
Changed /plugin install to refresh a stale marketplace catalog and retry before reporting a plugin not found
Changed plugins installed from /plugin to activate immediately when safe, instead of always requiring /reload-plugins
Is this right?
0
0
Feedback
What's wrong with this entry?
Hard to understand Too vague Looks wrong Not relevant to me Too long Missing the detail I wanted Duplicate of another card
Clear Learned something new I can act on this Good catch
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
← Previous · 118 of 308
/mcp explains cross-session enable/disable drift
You'll notice MCP
In v2.1.221 Improvements release-page order
Next → · 120 of 308
Plugin validation warns about Claude Desktop marketplace compatibility
You'll notice Plugins