{"version":"2.1.287","anchor":"hooks-worker-crash-handling-now-per-module","canonical_anchor":"hooks-worker-crash-handling-now-per-module","heading":"Repeated hook crashes now switch off only the affected mods","tier":"notice","area":"Hooks","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287\/e\/hooks-worker-crash-handling-now-per-module","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287","markdown":"### Repeated hook crashes now switch off only the affected mods\n\nAfter repeated crashes in the hooks worker, only the mods running there are switched off, and anything they held back stays held back\n\n**Unclear.** It is not clear what counts as a mod here, or which hooks still run after the fallback.\n\n**What**\n\nHooks are commands or functions that Claude Code runs automatically at set points during a session. Some of them run in a separate background process called the hooks worker.\n\nBefore this change, if the hooks worker crashed, function hooks were switched off for the rest of the session. After repeated crashes that cannot be traced to one cause, Claude Code now switches off only the mods that run in the hooks worker. The message says that whatever those mods were holding back stays held back.\n\n**Why**\n\nLess is switched off when the worker fails. The message also makes clear that a crash does not let through anything the mods had blocked.\n\n- Area: Hooks\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5"}