{"version":"2.1.260","anchor":"api-client-now-sends-anthropic-beta-custom-header-value-only","canonical_anchor":"api-client-now-sends-anthropic-beta-custom-header-value-only","heading":"API client now sends anthropic-beta custom header value only when a flag is on","tier":"internal","area":"API Configuration","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.260\/e\/api-client-now-sends-anthropic-beta-custom-header-value-only","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.260","markdown":"### API client now sends anthropic-beta custom header value only when a flag is on\n\nA custom anthropic-beta header can be forwarded, but only once a gate is enabled.\n\nOutgoing Anthropic API requests now merge in a header set from a new `Cv()` function, which forwards a custom `anthropic-beta` header from `ANTHROPIC_CUSTOM_HEADERS` only with its value stripped, and only when a gate is enabled; otherwise it returns an empty object. This matches the existing behavior of stripping custom `Authorization` headers.\n\n- Area: API Configuration\n- Names: `ANTHROPIC_CUSTOM_HEADERS`\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Present in the build but not switched on"}