{"version":"2.1.285","anchor":"gatewayccr-requests-choose-host-ccr-gateway","canonical_anchor":"gatewayccr-requests-choose-host-ccr-gateway","heading":"Some requests now name a gateway or API host","tier":"internal","area":"Gateway","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285\/e\/gatewayccr-requests-choose-host-ccr-gateway","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285","markdown":"### Some requests now name a gateway or API host\n\nOne kind of request now says whether it goes to `ccr-gateway` or `api`, depending on the kind of session\n\n**Unclear.** The conditions that pick each host, and which users this reaches, are not known.\n\n**What**\n\nOne kind of request Claude Code sends now names the host it is meant for: `ccr-gateway` or `api`, chosen by a check on the current session. Before, it named no host. The code that reads `CLAUDE_GATEWAY_ALLOW_LOOPBACK` also moved again.\n\n**Why**\n\nThis may change where some requests go when Claude Code runs in a hosted session.\n\n- Area: Gateway\n- Names: `CLAUDE_GATEWAY_ALLOW_LOOPBACK`\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5"}