Add Example Notebook: Context-Aware Support Ticket Assistant (Explicit Context Management) #1125
Description
Description of the feature request:
I’d like to propose a new Gemini Cookbook example that demonstrates context management in a realistic, long running application scenario.
The example is a context-aware support ticket assistant that:
- maintains structured ticket state (open / resolved)
- tracks attempted fixes
- summarizes prior conversation into long-term memory
- reuses that context when the ticket is reopened
A key goal of the example is to make context awareness visibly obvious.
What problem are you trying to solve with this feature?
Many developers struggle with understanding how to manage context explicitly when building Gemini powered applications that go beyond short chats.
While Gemini supports very large context windows, there aren’t currently Cookbook examples that show:
- what information should be stored as structured state vs. free text
- how prior context should change assistant behavior (not just be repeated)
This example aims to provide a simple pattern for context aware design that developers can adapt to real world use cases like support systems or agent workflows.
Any other information you'd like to share?
I’ve put together a working example in a separate repository (It is only a simple draft right now for seeking feedback on the content).
I’m open to any feedback and whether this fits the Cookbook scope, how the example could be simplified or refined and whether there is something I should change.