{"version":"2.1.284","anchor":"feature-flag-client-now-records-whether-a-non-default-api-ho","canonical_anchor":"feature-flag-client-now-records-whether-a-non-default-api-ho","heading":"Claude Code now notes when it has talked to an API host other than Anthropic's","tier":"internal","area":"Internals","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.284\/e\/feature-flag-client-now-records-whether-a-non-default-api-ho","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.284","markdown":"### Claude Code now notes when it has talked to an API host other than Anthropic's\n\nThe part of Claude Code that fetches feature settings now remembers whether any request went to a host other than https:\/\/api.anthropic.com\/\n\n**Unclear.** It is not clear which part of Claude Code reads this record or what it does differently as a result.\n\n**What**\n\nClaude Code fetches feature settings from a server. The part that does this now keeps a record of whether any of those requests went to a web address other than the standard Anthropic one, `https:\/\/api.anthropic.com\/`. Once a single request has gone somewhere else, for example through a company proxy or gateway, that record stays set for the rest of the run, and other parts of Claude Code can check it.\n\n**Why**\n\nIn practice, Claude Code can now tell whether it has been reaching Anthropic directly or through a different address. That matters mostly to people who route Claude Code through a proxy or gateway, since their setup can now be recognised as different from a direct connection.\n\n- Area: Internals\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5"}