Follow Discord
Sweep 27 Oct 2026 · 19:04Z Build v2.1.312 531 read Stable v2.1.308 Latest v2.1.312 Next v2.1.312 Feeds RSS JSON llms.txt llms-full.txt Unofficial
HomeReleasesv2.1.311entry #413

Claude Code v2.1.311 ·

Gateway logs now record a second upstream request ID

The gateway now captures the upstream apim-request-id header, logs it, and strips it and the existing request ID from responses

Under the hood Internal Changes
JSON All of v2.1.311
Under the hoodTier: how much it should matter to you
1Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
GatewayArea: what it touches
Internal ChangesKind: in v2.1.311,
Internal ChangesSection of the release

Unclear Whether this gateway runs for ordinary Claude Code users is not stated.

What

The gateway previously captured only the upstream request-id header. It now also copies the upstream apim-request-id header into x-gateway-upstream-cloud-request-id.

  • The value is checked against a pattern and logged as upstream_cloud_request_id on the line recorded for each model request.
  • Both x-gateway-upstream-cloud-request-id and x-gateway-upstream-request-id are removed from responses before they go out.
Why

When a request fails at a cloud service that sits in front of the model, such as Azure, the logs now hold an ID that can be matched with that service's own records.

How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtWhether this gateway runs for ordinary Claude Code users is not stated.

See this entry in the whole of v2.1.311 →

Feedback