fix(ts-sdk): default historyDbPath to ~/.mem0/history.db instead of r…

[shafdev]

Linked Issue

Closes #5004

Description

Default historyDbPath was set to "memory.db" (relative), causing
better-sqlite3 to create a fresh SQLite file in every CWD. Mirrors the
existing getDefaultVectorStoreDbPath() pattern — now defaults to
~/.mem0/history.db.

Type of Change

• Bug fix (non-breaking change that fixes an issue)
• New feature (non-breaking change that adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Refactor (no functional changes)
• Documentation update

Breaking Changes

N/A

Test Coverage

• I added/updated unit tests
• I added/updated integration tests
• I tested manually (describe below)
• No tests needed (explain why)

Checklist

• My code follows the project's style guidelines
• I have performed a self-review of my code
• I have added tests that prove my fix/feature works
• New and existing tests pass locally
• I have updated documentation if needed

[PHclaw]

Nice fix! Using ~/.mem0/history.db as default is much better than a relative path.

One suggestion: consider using os.path.expanduser() explicitly in case the runtime doesn't expand ~:

default_path = os.path.expanduser('~/.mem0/history.db')

Also, it would be good to ensure the parent directory exists:

os.makedirs(os.path.dirname(default_path), exist_ok=True)

This prevents FileNotFoundError on first run.

[shafdev]

Thanks for taking a look! Both points are already handled in the current implementation:

1. ~ expansion — this is the TypeScript SDK, so we use Node's built-in os.homedir(), which returns the fully-resolved absolute path (e.g. /Users/alice) directly. The ~ literal is never used in the code, so there's nothing to expand.

   // mem0-ts/src/oss/src/utils/sqlite.ts
   export function getDefaultHistoryDbPath(): string {
     return path.join(os.homedir(), ".mem0", "history.db");
   }

2. Parent directory creation — SQLiteManager's constructor already calls ensureSQLiteDirectory(dbPath) before opening the database, which does fs.mkdirSync(path.dirname(dbPath), { recursive: true }). So ~/.mem0/ is auto-created on first run.

   // mem0-ts/src/oss/src/storage/SQLiteManager.ts
   constructor(dbPath: string) {
     ensureSQLiteDirectory(dbPath);
     this.db = new Database(dbPath);
     this.init();
   }

For reference, the Python SDK does the equivalent — os.path.expanduser("~") in mem0/configs/base.py and os.makedirs(mem0_dir, exist_ok=True) in mem0/memory/setup.py. This TS fix mirrors that exact behaviour.