Source Intelligence
Follow Discord

DisclaimerUnofficial, and not affiliated with Anthropic. Nearly all of this is read straight out of what ships: npm bundles, captured prompts, published docs. Anthropic's own notes go in verbatim, marked as theirs. The rest is my reading, and every entry carries the strings behind it. If one looks wrong, vote it down and say why.

← All of v2.1.228 Home All releases ←olderv2.1.227 v2.1.229newer→
Claude Code v2.1.228

Gateway config now rejects unsafe customer-routed-inference setups

You'll notice
Useful2 Signal3
Gateway not in their notes

Gateway config refuses to start with an empty audience or organization allowlist.

oidc
What

Operator config parsing fails a deployment that enables customer-routed inference with an empty audience list or an empty organization allowlist. oidc is now required unless customer-routed inference is enabled.

Details
  • The rejection messages spell out the reason: audience binding is what stops a token minted for another organization's gateway from being replayed against yours.
Evidence

oidc is required \u2014 it may be omitted only for a customer-routed-inference-only deployment (cri.enabled: true)

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

Related

Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.

See this entry in the whole of v2.1.228 →