{"version":"2.1.280","anchor":"hook-timeout-message-now-names-the-timed-out-command","canonical_anchor":"hook-timeout-message-now-names-the-timed-out-command","heading":"Hook-timeout message now names the timed-out command","tier":"notice","area":"Hooks","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/hook-timeout-message-now-names-the-timed-out-command","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### Hook-timeout message now names the timed-out command\n\nHook timeout warnings now show which specific command timed out\n\n**What**\n\nWhen a hook (a custom script Claude Code runs automatically at certain points) takes too long and times out, the warning message shown in the transcript now includes the specific command that was running, in brackets, before saying it timed out. Previously the message only named the hook, not the command it ran.\n\n**Why**\n\nThis makes it much easier to identify and fix the exact command that's causing a timeout, especially if a hook runs several commands.\n\n- Area: Hooks\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}