Compressing Gemini API Chat History with Rolling Summaries — Designing Chatbots That Survive Hundreds of Turns
When a Gemini chatbot grows long enough, your bills balloon and one day a request hits the token ceiling. The rolling-summary pattern keeps long chats stable.
Why per-turn generationConfig is ignored in Gemini API chat sessions
If you pass a different generationConfig (temperature, max_output_tokens, response_schema) to each send_message in a google-genai chat session and the behavior never changes, this walkthrough shows what is actually happening, why the SDK is designed that way, and three workarounds we use in production for review-summary and reply-draft pipelines.
Why 'contents must alternate between user and model' Won't Go Away in the Gemini API — and How to Fix It
A focused guide to the Gemini API's 'contents must alternate between user and model' error — what really triggers it, why role names from OpenAI break it, and how to fix Function Calling and system_instruction pitfalls with copy-pasteable code.
Gemini API Multi-Turn Chat Breaking: Chat History Management Pitfalls and Fixes
When building multi-turn conversations with the Gemini API, longer chats cause token overflow, slowdowns, and context loss. Learn how to use ChatSession correctly with practical code examples for managing chat history.