Skip to main content
The stores below share a StorageDriver through UnifiedMemoryConfig. Enable them for an application requirement, not as an all-features preset. Vector and graph backends remain separate resources.

​
Summaries

summaries: true is the default once unified memory is enabled. Optional maxCount and maxTokens control retained summaries and their context. Summary guide.

​
User Facts

userFacts: true enables user-scoped facts. The optional maxFacts defaults to 100. Facts guide.

​
User Profile

userProfile: { customFields: ["department"] } adds application-specific profile fields. Profile guide.

​
Entity Memory

entities: { namespace: "support" } selects an entity namespace. Direct APIs require a user ID; the host verifies it. Entity guide.

​
Decision Log

decisions: { maxContextDecisions: 5 } limits decisions injected into context. Decision guide.

​
Learned Knowledge

learnings requires a configured VectorStore. Collection, retrieval count, and relevance floor belong to the memory feature, not necessarily the vector driver’s constructor.

​
Correction Capture

corrections uses the same vector interface, with its own collection and retrieval settings. Recording a correction makes it available for future retrieval; it cannot guarantee the model never repeats an error. Correction guide. The following host factory accepts its already selected model, storage, and vector backend. It exposes the exact composition without inventing backend constructor fields:
The host chooses and authorizes the store scope, configures its embedding provider, and owns shared connections. For Qdrant, the embedder is a second constructor argument, not a config property: new QdrantVectorStore(config, embedder). Follow vector-store setup for optional dependencies.

​
Graph Memory

graph: { store, autoExtract: true, maxContextNodes: 10 } enables graph-backed context. There is no unified-memory maxDepth option. Graph guide.

​
Procedure Memory

procedures: { maxProcedures: 50 } stores suggested sequences. Its matching and ownership differ from vector learnings. Procedure guide.

​
Temporal Awareness

Facts and graph relationships have store-specific validity metadata. Use the appropriate read methods for current versus historical records. There is no universal includeSuperseded memory switch. Temporal guide.

​
All Auto-Exposed Tools

Enabled features contribute their own tools. Inspect the actual tools available to your Agent and apply execution policy to them; the presence of memory tools does not exempt reads or writes from your application’s authorization rules. Continue with isolation, budgets, and maintenance.