Migration

What is it?

Guides for moving to Wolbarg — including the AgentOrc → Wolbarg rebrand (0.3) and the 0.1 → 0.2 constructor changes.

0.3 — AgentOrc → Wolbarg

npm uninstall agentorc
npm install wolbarg

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

// after
import { Wolbarg } from "wolbarg";
const ctx = new Wolbarg({ /* … */ });

• Class / options / error: AgentOrc* → Wolbarg*
• Site: wolbarg.com
• GitHub: Atharvmunde11/wolbarg
• Internal meta table: agentorc_meta → wolbarg_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)
const ctx = new Wolbarg({
  organization,
  storage: sqlite(database.connectionString),
  embedding: openaiEmbedding({ /* … */ }),
  llm: openaiLlm({ /* … */ }), // optional
});

// 0.2 — init() still works for compatibility

Schema

SQLite auto-migrates to schema version 2 (FTS5). Existing databases open without manual steps. Embedding dimension changes still require a fresh DB.

Method names (remember / recall / …) are unchanged. New optional recall fields are additive.

Upgrade

npm install wolbarg@^0.3.0

Related pages

• What's New in 0.2
• init() Compatibility
• Limitations