Description

Fixes SQLite path handling bugs in OSS mode for the TypeScript SDK.

Fixes #4290
Fixes #4080
Fixes #4096

Problem

There are two SQLite path bugs in OSS mode that cause failures in daemon/service/container environments:

Bug 1: historyDbPath is silently ignored

ConfigManager.mergeConfig() always spreads DEFAULT_MEMORY_CONFIG.historyStore (which hardcodes historyDbPath: "memory.db") into the merged config. Since spreading undefined over the default is a no-op, historyStore is always truthy after merging. The Memory constructor then always takes the historyStore branch, making the top-level historyDbPath dead code.

// User sets this...
const m = new Memory({ historyDbPath: "/data/history.db" });

// ...but mergeConfig always produces this:
historyStore: { provider: "sqlite", config: { historyDbPath: "memory.db" } }  // default wins

// Memory constructor always takes this branch (historyStore is always truthy):
this.db = HistoryManagerFactory.create(this.config.historyStore.provider, this.config.historyStore);
// → opens "memory.db" relative to CWD, ignoring the user's "/data/history.db"

Bug 2: vector_store.db hardcoded to process.cwd()

MemoryVectorStore defaults to path.join(process.cwd(), "vector_store.db"), which fails when CWD is / or not writable — common in LaunchAgent, systemd, and container environments.

Solution

• Propagate historyDbPath into historyStore.config.historyDbPath during config merging with correct precedence: explicit historyStore.config > top-level historyDbPath shorthand > default memory.db
• Only spread default sqlite config for sqlite providers — prevents historyDbPath: "memory.db" from leaking into supabase/other provider configs
• Default vector store path to ~/.mem0/vector_store.db instead of process.cwd()/vector_store.db
• Emit a migration warning when an existing vector_store.db is found at the old CWD-based location
• Auto-create parent directories for file-backed SQLite databases before opening them
• Remove dead code in the Memory constructor — the defaultConfig fallback was unreachable since historyStore is always populated after config merging
• Add dbPath to VectorStoreConfig interface and zod schema

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Refactor (does not change functionality, e.g. code style improvements, linting)
• Documentation update

How Has This Been Tested?

• Unit Test
• Test Script (please provide)

Commands run locally:

cd mem0-ts
npm test -- --runInBand \
  src/oss/src/tests/sqlite-path-resolution.test.ts \
  src/oss/src/tests/sqlite-backward-compat.test.ts \
  src/oss/src/tests/better-sqlite3-migration.test.ts

65 tests total — all passing (41 new + 24 existing, 0 regressions).

New tests: sqlite-path-resolution.test.ts — 19 tests

Config merging (6):

SQLiteManager (3):

MemoryVectorStore (5):

Utilities (5):

New tests: sqlite-backward-compat.test.ts — 22 tests

Existing tests: better-sqlite3-migration.test.ts — 24 tests, all passing

No regressions.

Note: npm test -- --runInBand for the entire mem0-ts package still hits pre-existing failures in unrelated integration-style tests (src/client/tests/memoryClient.test.ts, src/oss/tests/memory.test.ts) that require external services / outdated call signatures. This PR does not modify those areas.

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published in downstream modules
• I have checked my code and corrected any misspellings

Maintainer Checklist

• closes [Bug] historyDbPath ignored in open-source mode — SQLite always uses relative "memory.db" + vector_store.db uses process.cwd() #4290
• closes historyDbPath top-level config field is silently ignored (historyStore default always takes precedence) #4080
• closes Node SDK OSS: historyDbPath config ignored, SQLite history always opens at default memory.db #4096
• Made sure Checks passed