Concepts
What Wolbarg is, why it exists, and the provider philosophy behind its architecture.
Ready to code? Start with the Quick Start — remember/recall in under a minute.
What is Wolbarg?
Wolbarg is a TypeScript SDK that gives AI agents a shared, persistent semantic memory. Store facts with remember(), retrieve them with recall(), optionally ingest documents, compress memories with an LLM, and react to changes with subscribe().
Everything is built around replaceable providers: storage, embeddings, keyword search, rerankers, OCR, vision, chunking, and telemetry. The public API stays small; you swap backends by changing factory calls, not agent logic.
Why does it exist?
Most agent stacks either bolt memory onto a chat transcript or depend on a hosted vector database. Wolbarg sits in between: a shared semantic memory layer for multi-agent systems, with explicit providers, durable writes, and hybrid retrieval — plus connectors for Cursor and AI SDKs.
Core philosophy
- Everything is configurable — swap any provider.
- Nothing is required unless necessary — only
organization,storage, andembedding. - Optional features fail cleanly —
hybrid: true/rerank: truewithout their providers throwValidationError(fail-closed since 0.6.0);compresswithoutllmis aProviderNotConfiguredError. - Isolate providers in your app — keep factories in a dedicated folder so switching SQLite ↔ Postgres is a one-file change. See Project layout.
Capabilities
- Constructor DI + factories — SQLite / PostgreSQL storage, hybrid recall, metadata filters, MMR, rerankers, document
ingest, chunking, optional LLM compression - Telemetry — independent event database + trace IDs · Observability
- Wolbarg Studio — local read-only observability dashboard · Observability & Studio
- Checkpoints —
checkpoint/rollback/listCheckpoints(SQLite file-backed, single-org) - Import / export — portable SQLite memory bundles (single-org)
- Batch APIs —
rememberBatch/recallBatch - Recall explain — ranking diagnostics + timings
subscribe()— real-time memory change events · Real-time events- AbortSignal — cancellation on remember / recall / update / compress / forget
- Concurrency hardening — multi-writer SQLite retries · Concurrency
- Embedding cache — transparent reuse · Embedding cache
- Memory upsert / dedupe — update-instead-of-insert · Memory upsert
What it is not
- Not an agent / orchestration framework
- Not a hosted vector database SaaS
- Not a chat UI (Studio is a separate local observability app)
- Not a graph database — graph memory APIs were removed in 0.6.0
For out-of-the-box shared project truth in Cursor / Claude Code / Codex, see Wolbarg Workspace (@wolbarg/workspace).
When should you use it?
Use Wolbarg when multiple agents (or one long-running agent) need durable, searchable memory with clear backends and no infrastructure lock-in.