You'll noticeTier: how much it should matter to you
4Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
API ErrorsArea: what it touches
New FeaturesKind: in v2.1.248,
What probably matters to youSection of the release
What
An empty or malformed API response now raises a dedicated error that names what the body actually was and points at intermediaries between you and the API. It recognises common gateways (litellm, helicone, portkey, cloudflare-ai-gateway, kong, braintrust), Databricks hosts, reverse proxies identified by their Server: header (cloudflare, envoy, nginx, apigee, akamai, zscaler and others), and Apigee fault codes, and preserves hop headers in the report. Live on this build with no flag.
Details
One diagnosed case is a non-streaming request answered with an event stream, which is called out by name.
Evidence
body is an event stream (the non-streaming request was answered with a stream)
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
