Saurav Panda df063f9068 feat(llm/google): forward cached_content into generate_content ...

Adds a cached_content field on ChatGoogle (and a per-call kwarg on
ainvoke) that gets threaded into the GenerateContentConfigDict before
each generate_content call. This lets callers point Gemini at an
explicit CachedContent resource (e.g. "cachedContents/abc123") instead
of relying on implicit caching, which is constrained by the ~5-minute
TTL window.

Token accounting already pulls cached_content_token_count from
response.usage_metadata into ChatInvokeUsage.prompt_cached_tokens, so
the savings show up in usage stats without further work.

Cache creation itself (client.caches.create) is left to the caller —
this PR only adds the forwarding hook so explicit caching becomes
opt-in usable. A follow-up can wire agent-side cache lifecycle if
useful.

2026-05-22 17:54:04 -07:00

..

model_test_helper.py

api key not required

2025-10-25 18:00:18 -07:00

test_azure_responses_api.py

feat: add support for openai responses model

2025-12-22 22:16:56 -08:00

test_llm_anthropic.py

Split model tests

2025-10-25 10:16:46 -07:00

test_llm_azure.py

Api key rename

2025-10-25 10:24:40 -07:00

test_llm_browseruse.py

Split model tests

2025-10-25 10:16:46 -07:00

test_llm_google.py

feat(llm/google): forward cached_content into generate_content

2026-05-22 17:54:04 -07:00

test_llm_openai.py

Split model tests

2025-10-25 10:16:46 -07:00

test_llm_schema_optimizer.py

Remove stripping of required fields from gemini optimized schema

2025-10-31 15:54:51 -04:00