{"version":"2.1.268","anchor":"plugin-config-save-confirmation-no-longer-tells-users-to-run","canonical_anchor":"plugin-settings-view-prompts-a-reload-after-changes-that-nee","heading":"Plugin settings now manage reloads automatically instead of telling you to run \/reload-plugins","tier":"notice","area":"Plugins","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268\/e\/plugin-config-save-confirmation-no-longer-tells-users-to-run","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268","markdown":"### Plugin settings now manage reloads automatically instead of telling you to run \/reload-plugins\n\nSaving plugin settings no longer tells you to run \/reload-plugins by hand; the app now prompts or queues the reload itself\n\n**What**\n\n- The plugin settings screen now tracks whether a change you made needs a reload, and when you exit, it either does nothing, queues a deferred reload, or takes you straight into `\/reload-plugins`, depending on what changed.\n\n- The confirmation message shown after saving plugin configuration (for both the regular schema-based config flow and the MCPB config flow) was shortened from telling you to run `\/reload-plugins` yourself to a simple \"Configuration saved.\" The enable\/configure success message now uses a dynamic suffix instead of a hardcoded instruction to run `\/reload-plugins`.\n\n**Why** Previously you had to remember to manually run `\/reload-plugins` after changing plugin settings. Now Claude Code tracks that need for you and either handles it automatically or prompts you at the right moment.\n\n- Area: Plugins\n- Names: `\/reload-plugins`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}