feat: send custom HTTP headers on Anthropic provider requests - #645
Open
Ueslei Lima (uesleilima) wants to merge 1 commit into
Open
feat: send custom HTTP headers on Anthropic provider requests#645Ueslei Lima (uesleilima) wants to merge 1 commit into
Ueslei Lima (uesleilima) wants to merge 1 commit into
Conversation
Co-authored-by: Cursor <cursoragent@cursor.com>
🦋 Changeset detectedLatest commit: 9c389a1 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What and why
Anthropic-compatible enterprise gateways often require extra HTTP headers (tenant ID, APIM subscription key,
anthropic-version) beyond the API key. This PR addsOPENWIKI_PROVIDER_DEFAULT_HEADERS, a JSON object of header names to string values, and sends them on every Anthropic request viaclientOptions.defaultHeaders.When a custom Anthropic
baseURLis set, the client also enablesstreamingandstreamUsageso gateway transports that reject non-streaming requests still work.Header values can contain secrets, so the env var is persisted as a managed key but treated as a secret: diagnostics redact it, and debug dumps report length only (no preview).
How tested
resolveProviderDefaultHeaders(empty/invalid JSON, non-string values, invalid header names, successful parse).createModeltests for default headers and streaming-when-custom-base-URL (and that neither is forced against api.anthropic.com).pnpm run format,pnpm run lint,pnpm test(174 files passed, 2340 tests passed).Changeset
Minor changeset in
.changeset/anthropic-default-headers.md— user-facing feature.Historical context
This was previously bundled with an Anthropic-on-Azure-Foundry provider in #55. This PR isolates custom Anthropic headers (and the related custom-base-URL streaming tweak) as a single concern per CONTRIBUTING.md. It does not add a Foundry provider or HTTP proxy support.