{"version":"2.1.221","anchor":"installed-plugins-activate-in-place-instead-of-waiting-for-r","canonical_anchor":"installed-plugins-activate-in-place-instead-of-waiting-for-r","heading":"Installed plugins activate in place instead of waiting for \/reload-plugins","tier":"use","area":"Plugins","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.221\/e\/installed-plugins-activate-in-place-instead-of-waiting-for-r","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.221","markdown":"### Installed plugins activate in place instead of waiting for \/reload-plugins\n\nPlugins you install from \/plugin now activate immediately instead of making you run \/reload-plugins.\n\n**What**\n\nFinishing an install from the \/plugin flow now reloads plugins in the running session and tells you the result, so a freshly installed plugin is usable without a separate reload step.\n\n**Details**\n\n- Shows an \"Activating plugin\u2026\" spinner while the in-session reload runs.\n- Completion message reports the outcome: \" Plugin is now active.\" on success, \" The plugin couldn't be loaded \u2014 see \/plugin for details.\" on a load error.\n- Falls back to \" Run \/reload-plugins to apply.\" only when activation cannot be attempted, including when the live plugin-state getter is not available.\n- Activation is skipped, falling back to reload-required, when the reload reports `wouldInvalidateCache`, i.e. it would bust the prompt cache.\n- No flag guards this; it is reachable for everyone on this build.\n\n**Usage**\n\n`\/plugin` **Evidence** ` Plugin is now active.`\n\n- Area: Plugins\n- Names: `\/plugin`, `\/reload-plugins`\n- Tier: Use it now\n- Useful: 4\/5\n- Signal: 0\/5"}