{"version":"2.1.309","anchor":"hooks-worker-start-up-hang-detection","canonical_anchor":"hooks-worker-start-up-hang-detection","heading":"Slow-starting hooks worker is no longer mistaken for a stuck one","tier":"notice","area":"Hooks","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.309\/e\/hooks-worker-start-up-hang-detection","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.309","markdown":"### Slow-starting hooks worker is no longer mistaken for a stuck one\n\nClaude Code now waits for the hooks worker to come online before checking it, and reports a separate error if it never starts\n\n**What**\n\nHooks are commands you set up to run at certain points, and Claude Code runs them in a separate background worker. A watchdog checks that this worker still responds. The watchdog now has a starting phase, which ends when the worker reports that it is online. If the worker does not come online within half of the total time allowed, Claude Code reports that it did not come online, a different reason from a worker that stops answering later.\n\nA worker that is just slow to wake up at start no longer uses up the time meant for its regular responsiveness checks.\n\n**Why**\n\nHook workers that start slowly are no longer wrongly reported as stuck.\n\n- Area: Hooks\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}