You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
GatewayArea: what it touches
ImprovementsKind: in v2.1.283,
ImprovementsSection of the release
What
The check that refuses the forward_user_identity option on Anthropic upstreams now covers one more host. A gateway config now fails validation, the check Claude Code runs on the config before using it, when the upstream's base_url host is claude.googleapis.com.
The refused hosts are now:
anthropic.com and any subdomain of it
the AWS external-Anthropic endpoints
claude.googleapis.com, which is the addition
Why
If your gateway config sets forward_user_identity on an upstream pointing at claude.googleapis.com, that config will stop passing validation. The refusal keeps user emails from being sent to Anthropic. Remove the option from that upstream to fix it.
