WOLBΛRG

Migration

Upgrade Wolbarg — 0.5 → 0.6 production hardening, earlier additive upgrades, and AgentOrc → Wolbarg rebrand notes.

What is it?

Guides for moving between Wolbarg releases. Start with 0.5 → 0.6 if you are current; older sections cover earlier upgrades.

0.5 → 0.6 (breaking)

npm install wolbarg@0.6.0
# remove if you only used it for Wolbarg graph
npm uninstall neo4j-driver
AreaAction
Graph APIsRemove graph, sqliteGraph, neo4jGraph, linkMemories, getRelated, includeGraph
Hybrid / rerankEnsure keywordSearch / reranker are configured when flags are set — fail-closed
Rerank errorsCatch RerankError instead of assuming soft / identity fallback
Postgres remoteExpect TLS (sslmode=require) unless you override with ssl
Pool sizeRaise maxPoolSize if you relied on the old default of 64 (now 20)
TelemetrySet captureQueries: true if you need query strings persisted
Multi-org SQLiteOne file per organization for export / checkpoint / import / rollback
AbortSignalOptional on remember / recall / update / compress / forget

From 0.5.x without graph:

npm install wolbarg@0.6.0

Most remember / recall call sites need no changes. Review hybrid, rerank, and Postgres SSL settings.

Deep dive: What's New · Production · Graph memory (removed).

0.4 → 0.5 (historical)

npm install wolbarg@^0.5.0

0.5 introduced optional graph memory. That layer was removed again in 0.6.0 — do not add new graph call sites. If you are jumping from 0.4 directly to 0.6, skip graph entirely and follow the 0.5 → 0.6 table above for fail-closed hybrid/rerank and Postgres defaults.

Feature (0.5)Status in 0.6
Graph memoryRemoved
linkMemories / getRelated / includeGraphRemoved
Framework adapters (@wolbarg/*)Separate packages — unchanged

0.3 → 0.4 (additive)

npm install wolbarg@^0.4.0

No required code changes. Schema migrates automatically on open.

FeatureDefaultAction needed
Embedding cacheOnDisable with embeddingCache: { enabled: false } if unwanted
Memory dedupe / upsertOffOpt in via memory.dedupe
concurrency tuningSensible defaultsOptional
subscribe() / update()Opt in when needed
RememberResult.actionAlways presentIgnore safely if unused

Behavior notes

  • remember() / rememberBatch() still return a full MemoryRecord; they additionally include action: "created" | "updated".
  • SQLite writers now use BEGIN IMMEDIATE — safer under multi-process contention; may change latency shape under lock storms (see Concurrency).
  • New history event "updated" appears when upserts run.

Guides: Concurrency · Real-time events · Embedding cache · Memory upsert.

0.3 — AgentOrc → Wolbarg

npm uninstall agentorc
npm install wolbarg
// before
import { AgentOrc } from "agentorc";
const ctx = new AgentOrc({ /* … */ });

// after
import { Wolbarg, wolbarg } from "wolbarg";
const ctx = wolbarg({ /* … */ });
  • Class / options / error: AgentOrc*Wolbarg*
  • Site: wolbarg.com
  • GitHub: wolbarg/wolbarg
  • Internal meta table: agentorc_metawolbarg_meta (recreate DBs or migrate)

0.1 → 0.2 breaking changes

  • llm is no longer required to operate the SDK
  • Constructor instances without llm do not type compress
  • stats().llmModel may be null
  • Package version is 0.2.x+

API mapping (0.1 → 0.2)

// 0.1
const ctx = new Wolbarg();
await ctx.init({ organization, database, embedding, llm });

// 0.2+ (recommended)
import { wolbarg, sqlite, openaiEmbedding, openaiLlm } from "wolbarg";

const ctx = wolbarg({
  organization,
  storage: sqlite("./memory.db"),
  embedding: openaiEmbedding({ /* … */ }),
  llm: openaiLlm({ /* … */ }), // optional
});

// init() still works for compatibility

Schema

VersionNotes
v2FTS5 hybrid
v3+content_hash, embedding_cache, history "updated"
v4drop unused global created_at index; strip archived vectors from ANN; add agent-active covering index

SQLite auto-migrates on open. Embedding dimension changes still require a fresh DB.

Method names (remember / recall / …) are unchanged. New optional fields are additive unless called out in the 0.5 → 0.6 section.