{"version":"2.1.287","anchor":"hooks-worker-close-events-now-reported-with-a-distinct-reaso","canonical_anchor":"hooks-worker-close-events-now-reported-with-a-distinct-reaso","heading":"Clearer message when the background process that runs hooks shuts down","tier":"notice","area":"Hooks","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287\/e\/hooks-worker-close-events-now-reported-with-a-distinct-reaso","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287","markdown":"### Clearer message when the background process that runs hooks shuts down\n\nWhen the hooks process closes, Claude Code now says it ended, with its exit code, instead of reporting that it died\n\n**Unclear.** It is not clear whether a close of the hooks process could actually happen in earlier builds.\n\n**What**\n\nHooks are commands you set up to run automatically at certain moments, and Claude Code runs them in a separate background process. When that process closes, Claude Code now reports that \"the hooks worker ended\", adding the close code when there is one. Before, a close was reported the same way as a crash, as \"the hooks worker died\", with a vague reason.\n\nFailure reports now also say what kind of event caused them:\n\n- `close_event`, when the process closed\n\n- `error_event`, when it reported an error\n\n- `bare_event`, when it sent an event with no details\n\n**Why**\n\nThis makes it easier to tell a normal shutdown of the hooks process from a crash when something goes wrong with your hooks.\n\n- Area: Hooks\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}