{"version":"2.1.260","anchor":"org-compliance-policy-can-silently-drop-custom-anthropic-bet","canonical_anchor":"org-compliance-policy-can-silently-drop-custom-anthropic-bet","heading":"Org compliance policy can silently drop custom anthropic-beta headers","tier":"notice","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.260\/e\/org-compliance-policy-can-silently-drop-custom-anthropic-bet","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.260","markdown":"### Org compliance policy can silently drop custom anthropic-beta headers\n\nHIPAA compliance mode now silently drops custom anthropic-beta headers and disables 1M-context.\n\nWhen HIPAA compliance mode is active, any `anthropic-beta` header set via `ANTHROPIC_CUSTOM_HEADERS` is now dropped, with a debug log noting that experimental betas are disabled by org policy. The same compliance gate now also forces the 1M-context beta detection to always return false, and the SDK's beta-header resolution logic gained a similar case that drops all experimental beta headers and logs when the org-compliance gate is active, distinct from the existing per-header filtering.\n\n- Area: Elsewhere\n- Names: `ANTHROPIC_CUSTOM_HEADERS`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}