{"version":"2.1.290","anchor":"hooks-worker-crash-handling-kept-verdicts-and-unloading-of","canonical_anchor":"hooks-worker-crash-handling-kept-verdicts-and-unloading-of","heading":"Hooks worker can unload a crashed environment and be replaced","tier":"notice","area":"Hooks","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290\/e\/hooks-worker-crash-handling-kept-verdicts-and-unloading-of","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290","markdown":"### Hooks worker can unload a crashed environment and be replaced\n\nWhen the background process that runs plugin hooks crashes, Claude Code can now unload the crashed environment and replace the process\n\n**Unclear.** What a user sees during this recovery, and whether anything switches it on or off, is unclear.\n\n**What**\n\nHooks are commands Claude Code runs automatically at set moments, and plugin hooks run in a separate background process. When that process crashes, Claude Code can now unload the crashed environment and replace the process with a new one.\n\n**Why**\n\nThis gives Claude Code a way to recover when the process running plugin hooks dies.\n\n- Area: Hooks\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}