The gateway's protocol document is now generated to match how your deployment is actually configured.
What's wrong with this entry?
The gateway used to serve one fixed protocol document at /protocol. It is now generated per deployment: the wording branches on whether an identity provider is configured, and a customer-routed-inference section covering token verification, forwarding rules and the capability_rejected error class is appended when CRI is on. Without an identity provider, the document notes that sign-in routes return 404.
text/markdown; charset=utf-8, # Claude Code gateway protocol
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.
-
v2.1.248
Control traffic survives a re-authentication instead of being dropped
Both mention protocol
-
v2.1.227
claude gatewaynow identifies itself as the gateway providerBoth mention gateway
-
v2.1.229
Gateway streaming keeps connections alive with pings
Both mention gateway