{"version":"2.1.271","anchor":"hooks-module-reload-flow-reworked-to-report-finer-grained-ou","canonical_anchor":"hooks-module-reload-flow-reworked-to-report-finer-grained-ou","heading":"Plugin reload flow reworked with finer-grained status reporting","tier":"notice","area":"Plugins","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271\/e\/hooks-module-reload-flow-reworked-to-report-finer-grained-ou","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271","markdown":"### Plugin reload flow reworked with finer-grained status reporting\n\nPlugin reloading now reports whether each hooks module reloaded, refused, or held, via a restructured sessionPlugins API\n\n**What**\n\n- `reloadPlugins` was replaced with a `sessionPlugins` object that exposes a `reload()` method (same behavior as before) plus a new `retarget()` method for repointing plugins.\n\n- Reloading a plugin's hooks manifest now returns a result that distinguishes whether to retry or stop, instead of a generic pass\/fail.\n\n- The `\/config` plugin-reload screen now reads each module's outcome (reloaded, refused, or held) to build its status message, rather than catching a generic error string.\n\n**Why** This gives clearer feedback when Claude Code reloads plugin hooks: instead of a vague error, you can see specifically whether a module reloaded successfully, was refused, or is being held, making it easier to diagnose plugin problems.\n\n- Area: Plugins\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}