{"version":"2.1.268","anchor":"plugin-enabledisable-toast-no-longer-hard-codes-run-reloa","canonical_anchor":"plugin-enabledisable-toast-no-longer-hard-codes-run-reloa","heading":"Plugin enable\/disable toast no longer hard-codes \"Run \/reload-plugins to apply.\"","tier":"notice","area":"Plugins","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268\/e\/plugin-enabledisable-toast-no-longer-hard-codes-run-reloa","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268","markdown":"### Plugin enable\/disable toast no longer hard-codes \"Run \/reload-plugins to apply.\"\n\nPlugin enable\/disable messages no longer always tell you to run \/reload-plugins\n\n**Unclear.** It is unclear what determines the replacement fragment shown in each case, or whether it still points to `\/reload-plugins` in most situations.\n\n**What**\n\nWhen you enable, disable, update, or uninstall a plugin, or disable\/uninstall one via a settings file, Claude Code used to always append the fixed instruction \"Run \/reload-plugins to apply.\" to the confirmation message. That fixed text is now gone, replaced by a fragment that is supplied separately depending on the situation.\n\n**Why**\n\nThis lets the confirmation message vary by context instead of always pointing you to `\/reload-plugins`, which is useful since `\/reload-plugins` lets you apply plugin changes without restarting Claude Code.\n\n- Area: Plugins\n- Names: `\/reload-plugins`\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}