{"version":"2.1.268","anchor":"reload-plugins-sdk-request-gains-a-hold-on-cache-impact-opti","canonical_anchor":"reload-plugins-sdk-request-gains-a-hold-on-cache-impact-opti","heading":"reload_plugins SDK request gains a hold_on_cache_impact option to avoid silent cache invalidation","tier":"use","area":"Plugins","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268\/e\/reload-plugins-sdk-request-gains-a-hold-on-cache-impact-opti","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268","markdown":"### reload_plugins SDK request gains a hold_on_cache_impact option to avoid silent cache invalidation\n\nreload_plugins can now hold off reloading if it would invalidate the prompt cache, via a new hold_on_cache_impact option\n\n**What**\n\nThe `reload_plugins` request (used by the `\/reload-plugins` command and by the SDK) now accepts an optional `hold_on_cache_impact` flag. When set, if reloading plugins would change the session's tool list in a way that invalidates the prompt cache (the cached record of the conversation-so-far that lets Claude skip reprocessing it), the reload is skipped instead of applied. The response then reports `held: true` along with a `cache_impact` breakdown of what would have changed: `mcp_servers_added`, `mcp_servers_removed`, or `lsp_tool_change`. The session keeps its current plugins in that case.\n\nThis mirrors a check the interactive `\/reload-plugins` command already makes before it asks for `--force`. In the Agent SDK, the equivalent `reloadPlugins()` call now accepts a `holdOnCacheImpact` flag that gets sent as this same option.\n\n**Why**\n\nThis lets SDK integrations and other callers opt into the same cache-safety check the interactive command already had, avoiding a silent, expensive cache invalidation when plugins change.\n\n- Area: Plugins\n- Names: `hold_on_cache_impact`, `reload_plugins`, `\/reload-plugins`\n- Tier: Use it now\n- Useful: 4\/5\n- Signal: 3\/5"}