{"version":"2.1.277","anchor":"hooks-worker-heartbeat-timeout-made-remotely-configurable","canonical_anchor":"hooks-worker-heartbeat-timeout-made-remotely-configurable","heading":"Hooks worker heartbeat timeout made remotely configurable","tier":"internal","area":"Hooks","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.277\/e\/hooks-worker-heartbeat-timeout-made-remotely-configurable","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.277","markdown":"### Hooks worker heartbeat timeout made remotely configurable\n\nThe timeout for detecting a stuck hooks worker can now be set remotely instead of always being fixed at 5 seconds\n\n**What**\n\nClaude Code runs a background \"hooks worker\" process to execute hooks (scripts that run automatically at certain points). It detects a stuck, unresponsive worker by checking whether it has answered a heartbeat check within a timeout. That timeout used to always be a fixed 5000 milliseconds. Now, as long as there are no pending loads or builds in progress, the timeout value can instead come from a remotely configured setting, falling back to the same 5-second default otherwise.\n\n**Why**\n\nThis lets the stuck-worker detection threshold be tuned remotely without needing a new release, while keeping a safe fallback during load or build activity.\n\n- Area: Hooks\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}