{"version":"2.1.278","anchor":"new-function-captures-custom-anthropic-base-url-host-for-fir","canonical_anchor":"new-function-captures-custom-anthropic-base-url-host-for-fir","heading":"New function captures custom ANTHROPIC_BASE_URL host for firstParty sessions","tier":"internal","area":"Auto Mode","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.278\/e\/new-function-captures-custom-anthropic-base-url-host-for-fir","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.278","markdown":"### New function captures custom ANTHROPIC_BASE_URL host for firstParty sessions\n\nA new helper captures the custom hostname when ANTHROPIC_BASE_URL points somewhere other than Anthropic's API\n\n**Unclear.** The finding doesn't say what consumes this captured hostname, only that it's produced in this specific case.\n\n**What**\n\nA new helper function returns the hostname from `ANTHROPIC_BASE_URL` in the specific case where the session is still classified as first-party but the base URL isn't `api.anthropic.com`, and no unix socket is in use.\n\n**Why**\n\nThis appears to support telemetry or diagnostics around proxy or gateway hosts that don't match Anthropic's usual API address, likely to help identify unrecognized custom endpoints.\n\n- Area: Auto Mode\n- Names: `ANTHROPIC_BASE_URL`\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}