Claude Code can now detect whether the current base URL points to a known LLM gateway or proxy service, such as litellm, helicone, portkey, cloudflare-ai-gateway, kong, braintrust, bifrost, or databricks. It does this either by recognizing the hostname or by noticing a gateway during an actual request.
When a gateway is detected, the billing notice text changes: instead of the usual message, it tells the admin that the session is ineligible because requests are going through that gateway, and links to a docs page (auto-mode-classifier-billing) explaining how to fix it.
This helps admins understand why a billing-related feature isn't working when their traffic is routed through a gateway or proxy, rather than leaving them with a generic or confusing notice.
tengu_velvet_heron Not enough to sayNothing here resolved what this flag was doing on this version, so nothing here should be read as on or off.
This account: no value returned · anonymous baseline: no value returned · compiled default in v2.1.278: on
These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.
Read once, for one account on one subscription tier, against v2.1.278. It isn't a statement about your account. What a flag value here can and cannot tell you
The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.
| `x-litellm-end-user-id` | The developer's email, when the IdP supplied one. |claude-apps-gateway-config see the edit
Anthropic's documentation has since written up litellm, on Claude apps gateway configuration.
New in this build: tengu_velvet_heron