{"version":"2.1.277","anchor":"hooks-module-reload-diagnostics-gain-a-human-readable-why-d","canonical_anchor":"hooks-module-reload-diagnostics-gain-a-human-readable-why-d","heading":"Hooks module-reload diagnostics gain a human-readable 'why did we refold' explainer","tier":"internal","area":"Hooks","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.277\/e\/hooks-module-reload-diagnostics-gain-a-human-readable-why-d","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.277","markdown":"### Hooks module-reload diagnostics gain a human-readable 'why did we refold' explainer\n\nHooks diagnostics now explain in plain language why the hooks list was recalculated\n\n**What**\n\nClaude Code can now generate a human-readable explanation of why its internal set of hooks (scripts that run automatically at certain points, often added by plugins) was recalculated (\"refolded\"). The explanation names which plugin's hooks changed and how \u2014 for example, loaded fresh, added to, or removed from the set \u2014 or notes that a plugin crashed leaving work withheld, or that the order of the kept modules changed.\n\n**Why**\n\nThis makes it easier to understand, when debugging, why the active set of hooks changed rather than just seeing that it did.\n\n- Area: Hooks\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}