feat: inject anthropic prompt cache control#162
Merged
Conversation
Author
E2E cache validationRan on 2026-06-28 from branch
Result: passed ( The E2E test uses a mock Anthropic upstream, so it validates gateway request/response behavior without spending real Anthropic tokens. It verifies top-level |
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.
Summary
Adds gateway-side Anthropic automatic prompt-cache control for native Anthropic requests when the client has not already supplied
cache_control.Changes
ANTHROPIC_PROMPT_CACHE_TTLsupport withoff,5m,1h, andautopoliciescache_controlon typed and raw Anthropic Messages paths, streaming paths, and Anthropic Responses requestscache_controlmarker anywhere in the request bodyType of change
Affected areas
How to test
Expected outcome: the Anthropic provider tests pass and cover top-level injection, client override preservation, header opt-out, auto workload TTL selection, and raw-body injection.
New configuration:
Screenshots/Recordings
Not applicable; backend provider behavior only.
Breaking changes
Related issues
None
Security considerations
The request headers used to control gateway policy are stripped before Anthropic passthrough forwarding. Client-provided
cache_controlremains authoritative and is not overwritten.Checklist
docs/contributing/README.mdand followed the guidelines