Add Agent Memory

Before the model: recall what is known about the user. After the turn: write the exchange back. The service extracts long-term memories from sessions. What it remembers, shares, excludes and retains is a service setting, not an SDK argument: ask first, provision, then wire.

1. Discover

Read the project:

• Find the turn (where the model is called) and the user id and session or thread id in scope there.
• Identify the framework from imports.
• Find existing memory code (BaseStore, InMemoryStore, custom dict or DB). You will replace its reads and writes, not the graph.
• Already on Redis Agent Memory through its own client? Inventory before changing anything: adapters over the generated redis_agent_memory client, an MCP client exposing memory tools to the model, a namespace string written on every record, and any second runtime or framework plugin writing the same store. See "Already on Redis Agent Memory" in step 4.
• Async agent? Use the a-prefixed methods.

Then ask the developer these five questions, nothing more. A shrug takes the default.