Under the hoodTier: how much it should matter to you
1Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
ElsewhereArea: what it touches
Internal ChangesKind: in v2.1.267,
Internal ChangesSection of the release
What
Claude Code's model gateway (the component that routes requests to an upstream AI provider) can be configured to forward a user's identity to the upstream. When a request made this way, using the 'raw' upstream kind with forwardUserIdentity and a resolvable user email, comes back with a 429 (rate limited) response, the gateway no longer marks it as a generic retryable error status.
Why
A 429 tied to a specific forwarded user's identity reflects that user's own rate limit rather than a generic gateway problem, so it no longer gets bucketed with other retryable gateway errors.
