You'll noticeTier: how much it should matter to you
4Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
API ErrorsArea: what it touches
ImprovementsKind: in v2.1.234,
What probably matters to youSection of the release
What
When the API returns something that is not a message, the error now fingerprints the responder instead of failing bare, and suggests checking for a proxy or gateway intercepting the request. Two new structured log events, cli_api_error and cli_api_retry, carry the same detail. This is aimed at corporate gateways sitting in front of the API.
Details
The fingerprint records content-type bucket, body kind (event stream, HTML, XML, JSON served under the wrong content type, and so on), byte size, and whether the request id looks Anthropic-issued.
A server-header classifier covers roughly 20 intermediaries including cloudflare, envoy, zscaler, squid, haproxy, netskope, bluecoat and big-ip, plus Apigee fault source and code taxonomies and the set of intermediary headers seen.
The log events include a route block: provider, whether the base URL is the default, an Anthropic one or custom, and whether an https proxy, custom headers, extra CA certificates or a client certificate are in use.
No flag guards this; it sits on the normal API error paths.
Evidence
check for a proxy or gateway intercepting the request.
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
