{"version":"2.1.323","anchor":"hooks-worker-crash-handling-and-plugin-install-commandoutput","canonical_anchor":"hooks-worker-crash-handling-and-plugin-install-commandoutput","heading":"Clearer messages when hooks fail to load and when plugins install","tier":"notice","area":"Hooks","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/hooks-worker-crash-handling-and-plugin-install-commandoutput","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### Clearer messages when hooks fail to load and when plugins install\n\nHook load failures after a restart now give a reason, and plugin install results can include command output and an older-version note\n\n**What**\n\nHooks are your own scripts or commands that Claude Code runs at set points. Claude Code runs some of them in a separate helper process, and these changes affect what that process reports:\n\n- The message shown when the helper process crashes no longer adds that anything the hooks withheld stays withheld until they are reloaded or disabled.\n\n- If a hooks module fails to load after the helper process restarts, Claude Code now reports a reason for the failure.\n\nWhen you install a plugin (an add-on that extends Claude Code), the install result can now also carry the output of commands run during the install and a note for when the install ends up on an older version.\n\n**Why**\n\nThis gives you more to go on when a hook or a plugin install goes wrong.\n\n- Area: Hooks\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}