Activating plugins from the /plugin dialog now warns you before it invalidates your conversation's prompt cache.
What's wrong with this entry?
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.
- The dialog is passed
getReloadCacheImpactOptions, carrying the model plus dynamic MCP config. - An install-triggered activation can now bail out with a
cache_impactoutcome. - The equivalent /reload-plugins warning text already existed.
getReloadCacheImpactOptions
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.229
Plugin auto-updates can now take effect without a restart
Both mention reload
-
v2.1.239
Skipped-plugin warning no longer overstates what it found
Both mention reload
-
v2.1.242
/reload-plugins now warns about LSP tool changes too
Both mention reload