The retry/error telemetry schema gained an optional no_response object with waited_ms and retry_wait_ms fields, populated only when the API sent no response headers within the first-byte timeout window (CLAUDE_STREAM_FIRST_BYTE_TIMEOUT_MS). This distinguishes a no-response timeout from a normal retry, reporting how long the failed attempt waited for headers and how long the retry will wait.
New no_response diagnostic field for stream timeouts
Telemetry schema now records how long a no-response stream timeout waited.
Under the hoodTier: how much it should matter to you
1Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
InternalsArea: what it touches
Internal ChangesKind: in v2.1.261,
Internal ChangesSection of the release