{"version":"2.1.278","anchor":"gatewayproxy-detection-feeding-the-billing-notice-message","canonical_anchor":"gatewayproxy-detection-feeding-the-billing-notice-message","heading":"Gateway\/proxy detection feeding the billing notice message","tier":"internal","area":"Auto Mode","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.278\/e\/gatewayproxy-detection-feeding-the-billing-notice-message","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.278","markdown":"### Gateway\/proxy detection feeding the billing notice message\n\nClaude Code now detects LLM gateways and swaps the billing notice for a gateway-specific message with a docs link\n\n**What**\n\nClaude 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.\n\nWhen 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.\n\n**Why**\n\nThis 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.\n\n- Flag `tengu_velvet_heron`: Not enough to say (read for one account on one subscription tier against v2.1.278; this account: no value returned, anonymous baseline: no value returned, compiled default: 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.\n- Area: Auto Mode\n- Names: `litellm`, `helicone`, `portkey`\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5"}