Graph memory
Graph memory was removed in Wolbarg 0.6.0. Use metadata or an external store for relationships.
Removed in 0.6.0
Graph memory is no longer part of the Wolbarg core SDK.
The following APIs and factories were removed:
sqliteGraph/neo4jGraphlinkMemories/getRelatedrecall({ includeGraph: true })neo4j-driverpeer dependency
This page is kept so existing links and bookmarks resolve. Full release notes: What's New · Migration.
What to use instead
| Need | Approach |
|---|---|
| Tag related facts | Store relation ids / keys in metadata and filter with meta.* |
| Explicit graph walks | Use an external graph database or your own edge tables outside Wolbarg |
| Similarity + keywords | Semantic search + hybrid BM25 |
await ctx.remember({
agent: "support",
content: { text: "Refund SLA is 5 business days." },
metadata: { topic: "billing", relatedTo: ["pref-email"] },
});
const hits = await ctx.recall({
query: "refund timeline",
filter: { metadata: meta.eq("topic", "billing") },
});Upgrade checklist
- Remove
graph,sqliteGraph,neo4jGraph,linkMemories,getRelated, andincludeGraphfrom your code - Uninstall
neo4j-driverif you only used it for Wolbarg - Install
wolbarg@0.6.0 - Re-express relationships with metadata or an external store
Related pages
Memory upsert & deduplication
Opt-in write-time exact and near-duplicate detection in Wolbarg 0.4 — update existing facts instead of inserting duplicates, with RememberResult.action and update().
Benchmarks
Methodology and published results for Wolbarg v0.4.0 — dual-backend v4 stress, embedding cache, multi-process concurrency, and how to reproduce locally.