Context
The MemoryHub MemoryStore protocol landed in kagenti/adk as PR kagenti/adk#231. Kagenti agents can now get governed, cross-session memory by adding kagenti-adk[memoryhub] and wiring the A2A extension. This is a natural addition to the course as a supplementary module.
What the module should cover
- Deploy kagenti to the cluster -- install the kagenti ADK server alongside the existing calculus agent stack
- Deploy MemoryHub -- stand up the MemoryHub service (or point at an existing instance)
- Wire MemoryStore into an agent -- use the
MemoryHubExtensionSpec / MemoryHubExtensionServer pattern from the SDK docs to give an agent durable memory
- Exercise it -- demonstrate search, create, and curation rejection in a running agent
- Client-side fulfillment -- show how a calling client supplies
MemoryHubFulfillment metadata (API key path and OAuth path)
Placement
This should be a supplementary module (not inserted into the core 00-11 track). Something like supplementary/kagenti-memoryhub.md or a new numbered module after the current track. The existing course stands alone without it.
References
Context
The MemoryHub
MemoryStoreprotocol landed in kagenti/adk as PR kagenti/adk#231. Kagenti agents can now get governed, cross-session memory by addingkagenti-adk[memoryhub]and wiring the A2A extension. This is a natural addition to the course as a supplementary module.What the module should cover
MemoryHubExtensionSpec/MemoryHubExtensionServerpattern from the SDK docs to give an agent durable memoryMemoryHubFulfillmentmetadata (API key path and OAuth path)Placement
This should be a supplementary module (not inserted into the core 00-11 track). Something like
supplementary/kagenti-memoryhub.mdor a new numbered module after the current track. The existing course stands alone without it.References
docs/development/sdk/memory.mdxfor the SDK referenceexamples/agent-integration/memoryhub/memoryhub-recall/for the working example