Memory convenience methods

MemoryManager offers convenience methods for common operations. They do not provide universal CRUD for every enabled store. Use a dedicated store API when you need precise ownership, sharing, or deletion semantics.

remember

remember(content, { userId?, scope?, importance? }) first writes a manual user fact when user facts are enabled and a user ID is supplied. Otherwise it tries learned knowledge, then a user-scoped entity fallback. Without a suitable store it can do nothing. For learned knowledge, scope is used as a context/namespace label; it is not a substitute for the record’s explicit sharing scope. Prefer the store’s saveLearning() API when choosing agent, tenant, or global visibility. Always pass the required owner identifiers.

recall

recall(query, { userId?, topK?, scope? }) returns { content, score, source } records. The default topK is 10. It gathers from supported facts, entities, learnings, and graph stores; it does not search all session turns, summaries, profiles, decisions, procedures, and corrections. Facts/entities require a user ID. The optional scope field is not an implemented universal authorization filter. Raw graph recall searches its configured backend; use a backend already scoped to the caller. For the filtered graph-memory prompt path, use its documented context methods instead. See scoring for the actual store-specific ranking signals. A composite score is not a calibrated probability that a fact is correct.

forget

Input	Operation
`userId` and `factId`	Remove that user’s fact
`userId` and `entityId`	Remove that user’s entity
`userId` without either record ID	Clear configured user facts and profile

An entity ID alone does not select an owner. The returned count reflects operations/store clearing, not an exact count of every erased record. scope does not implement broad scope deletion. This method does not erase sessions, vector indexes, graph stores, external artifacts, or all application data.

Full Example

Run this complete example with @agentium/core@4.0.0 and tsx. It needs no provider key:

import { InMemoryStorage, MemoryManager } from "@agentium/core";

const storage = new InMemoryStorage();
const memory = new MemoryManager({ storage, summaries: false, userFacts: true });
try {
  await memory.remember("Prefers metric units", { userId: "alice", importance: 0.7 });
  const hits = await memory.recall("metric", { userId: "alice", topK: 3 });
  console.log(hits.map((hit) => hit.content)); // ["Prefers metric units"]
  console.log(await memory.forget({ userId: "alice" })); // 1 configured store cleared
  console.log(await memory.recall("metric", { userId: "alice" })); // []
} finally {
  await storage.close();
}

Substitute a persistent driver only after testing the intended scope. Call these methods behind verified identity and resource authorization. For a complete application deletion operation, enumerate the data stores your application actually uses; see maintenance limits.

Build

Agent applications

Harness runtime

Teams and workflows

Data and capabilities

Interfaces and jobs

Voice and telephony

Verify and manage

Memory convenience methods

remember

recall

forget

Full Example

​remember

​recall

​forget

​Full Example

remember

recall

forget

Full Example