Add Gemini explicit caching support #50
Draft
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 support for Gemini's explicit context caching API, enabling significant token savings (up to 99.8%) for repeated requests with static content like system instructions, tool definitions, and reference documents.
Changes
cached_contentparameter toChat.__init__()to accept existing cache referencescreate_cache()- Create a new cache with system instructions, tools, and contentsdelete_cache()- Delete cache and clear cache stateupdate_cache()- Update cache TTLget_cache()- Retrieve cache metadata_call()to passcached_contentto litellm when cache exists_prep_msg()to exclude system instruction when it's already in cache-001suffix (e.g.,gemini-2.0-flash-001)Testing
All methods tested with Gemini API paid tier. Verified:
Related
Addresses request from community member regarding Gemini caching support.