{"version":"2.1.318","anchor":"mod-hot-reload-message-now-takes-the-whole-enabled-result","canonical_anchor":"mod-hot-reload-message-now-takes-the-whole-enabled-result","heading":"Mod hot-reload notice gains a case for mod hooks that did not load","tier":"notice","area":"Plugins","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318\/e\/mod-hot-reload-message-now-takes-the-whole-enabled-result","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318","markdown":"### Mod hot-reload notice gains a case for mod hooks that did not load\n\nThe notice shown after a mod is reloaded can now say a mod's hooks modules did not load, and that \/reload-plugins will not load them sooner\n\n**What**\n\nMods can be reloaded while Claude Code is running, without a restart. Afterwards Claude Code writes a notice saying what happened. The notice has changed in two ways.\n\n- A new case says that the mods' hooks modules did not load. Hooks are pieces of code that run automatically at set moments. The notice treats these as a person's own hooks modules, not an organization's, and says that `\/reload-plugins` does not load them any sooner. Before, the notice only had cases for reloaded, held, unbound and failed.\n\n- The message for a mod that was enabled now draws on the whole reload result instead of only its load status. The wording for the declined case is unchanged: it still says `\/reload-plugins` reloads only a mod that loaded at the start.\n\n**Why**\n\nWhen a mod you just wrote is not running, the notice now gives both you and Claude the actual reason: its hooks did not load. You can stop retrying `\/reload-plugins` expecting it to fix that. The wording Claude reports after writing a mod may also change slightly.\n\n- Area: Plugins\n- Names: `\/reload-plugins`\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}