{"version":"2.1.296","anchor":"startup-timing-stops-recording-hooks-init-ms-once-the-wait-i","canonical_anchor":"startup-timing-stops-recording-hooks-init-ms-once-the-wait-i","heading":"Startup timing for hooks stops updating after the wait is given up","tier":"internal","area":"Telemetry","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.296\/e\/startup-timing-stops-recording-hooks-init-ms-once-the-wait-i","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.296","markdown":"### Startup timing for hooks stops updating after the wait is given up\n\nClaude Code's startup timing no longer overwrites the hooks setup time after it has stopped waiting for hooks to be ready\n\n**What**\n\nClaude Code times parts of its own startup. One of those is how long hooks take to get ready. Hooks are commands Claude Code runs automatically at set moments. That time could be overwritten by later records. Once Claude Code has given up waiting for hooks, it now ignores later records of that time. It also notes where the hooks setup came from.\n\n**Why**\n\nThe startup timing for hooks becomes more accurate. It does not change how Claude Code starts.\n\n- Area: Telemetry\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 0\/5\n- Scope: individual\n- Heads-up: no"}