When 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.
Names in the bundleANTHROPIC_CUSTOM_HEADERS
The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.
Added since
A small documentation edit on Configure server-managed settings touched a line naming ANTHROPIC_CUSTOM_HEADERS after this was published.
Whether [`ANTHROPIC_CUSTOM_HEADERS`](/docs/en/env-vars#variables) needs approval also depends on the delivered value. Headers that only tag requests, such as `Accept-Language`, apply without the dialog. A line that names a credential, an o…server-managed-settings see the edit
Confirmed since
Anthropic's documentation has since written up ANTHROPIC_CUSTOM_HEADERS, on Connect Claude Code to an LLM gateway.
* **Amazon Bedrock, Google Cloud's Agent Platform, or Claude Platform on AWS**: add `ANTHROPIC_AUTH_TOKEN` after the block. Claude Code sends it to the gateway as an `Authorization: Bearer` header. For a credential in a different scheme or…llm-gateway-connect see the edit
One source agreesOne thing we can check says the same as this entry.
Anthropic's documentation agrees
Anthropic's documentation has since written up ANTHROPIC_CUSTOM_HEADERS, on Connect Claude Code to an LLM gateway.