{"version":"2.1.273","anchor":"new-gate-for-gateway-hint-headers-on-first-party-surfaces","canonical_anchor":"new-gate-for-gateway-hint-headers-on-first-party-surfaces","heading":"New gate for gateway hint headers on first-party surfaces","tier":"use","area":"Internals","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.273\/e\/new-gate-for-gateway-hint-headers-on-first-party-surfaces","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.273","markdown":"### New gate for gateway hint headers on first-party surfaces\n\nA new internal check decides when Claude Code sends extra gateway hint headers on first-party requests\n\n**Unclear.** What the gateway hint headers are used for once sent is not stated.\n\n**What**\n\nClaude Code has a new internal helper that decides whether to attach gateway hint headers to outgoing requests. It turns them on automatically if the `CLAUDE_CODE_GATEWAY_HINT_HEADERS` environment variable is set, or under another internal condition, turns them off entirely outside of \"first-party\" surfaces, and otherwise follows a feature flag.\n\n**Why**\n\nThis is an internal request-routing detail; it does not change anything a user needs to do.\n\n- Flag `tengu_splendid_sutton`: Not enough to say (read for one account on one subscription tier against v2.1.273; this account: no value returned, anonymous baseline: no value returned, compiled default: off) 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: Internals\n- Names: `CLAUDE_CODE_GATEWAY_HINT_HEADERS`\n- Tier: Use it now\n- Useful: 3\/5\n- Signal: 3\/5"}