InMemoryMemoryService
In-memory implementation of MemoryService for development and testing.
Uses keyword-based search with term overlap scoring. All data is stored in-process and lost on restart.
Implements
Section titled “Implements”Constructors
Section titled “Constructors”Constructor
Section titled “Constructor”new InMemoryMemoryService(): InMemoryMemoryService;Returns
Section titled “Returns”InMemoryMemoryService
Methods
Section titled “Methods”addSessionToMemory()
Section titled “addSessionToMemory()”addSessionToMemory(session, options?): Promise<void>;Ingest a session into long-term memory.
Typically called when a session ends or reaches a meaningful checkpoint. Implementations may store raw events, extract facts via LLM, or summarize. A session may be ingested multiple times (implementations must handle idempotency).
Parameters
Section titled “Parameters”| Parameter | Type | Description |
|---|---|---|
|
|
The session to ingest |
|
|
|
Optional ingestion configuration |
Returns
Section titled “Returns”Promise<void>
Implementation of
Section titled “Implementation of”MemoryService.addSessionToMemory
deleteMemories()
Section titled “deleteMemories()”deleteMemories(userId): Promise<void>;Delete all memories for a user. Used for GDPR compliance / data cleanup.
Parameters
Section titled “Parameters”| Parameter | Type |
|---|---|
|
|
|
Returns
Section titled “Returns”Promise<void>
Implementation of
Section titled “Implementation of”searchMemory()
Section titled “searchMemory()”searchMemory(request): Promise<SearchMemoryResponse>;Search long-term memory for relevant context.
Returns memories scoped to a specific user within an application context. Implementations may use keyword matching, semantic search, or hybrid approaches.
Parameters
Section titled “Parameters”| Parameter | Type | Description |
|---|---|---|
|
|
Search parameters (userId, query, optional filters) |
Returns
Section titled “Returns”Promise<SearchMemoryResponse>