{"version":"2.1.296","anchor":"host-unresponsive-warning-interval-fix-and-new-sessionstart","canonical_anchor":"host-unresponsive-warning-interval-fix-and-new-sessionstart","heading":"Hook timing diagnostics get a corrected interval and a resume wait measure","tier":"internal","area":"Telemetry","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.296\/e\/host-unresponsive-warning-interval-fix-and-new-sessionstart","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.296","markdown":"### Hook timing diagnostics get a corrected interval and a resume wait measure\n\nClaude Code's diagnostics now take the unresponsive-host interval from a different source and time how long resuming waits on `SessionStart` hooks\n\n**What**\n\nClaude Code records diagnostic data about how it is running. Three things changed in it:\n\n- The report sent when the host stops responding now takes its interval value from a different place than before.\n\n- A new timing mark measures how long resuming a session waits on `SessionStart` hooks, which are your own commands that run when a session begins or resumes.\n\n- A new marker records where hook setup was started from.\n\n**Why**\n\nIn practice, this makes Claude Code's own timing and health data more accurate.\n\n- Area: Telemetry\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}