Agent Memory is distributed as an ES module with optional peer dependencies for OpenClaw and node-llama-cpp; three CLI binaries—migrate-sqlite-to-tcvdb, export-tencent-vdb, and read-local-memory—are included for data migration and inspection tasks. The build process uses tsdown for the main plugin and tsc for CLI scripts; tests run via Vitest with watch and coverage modes available.
TencentDB-Agent-Memory is distributed as an ES module ("type": "module"), with ./dist/index.mjs as its main entry point.[1] The package is licensed under MIT.[1] TencentDB-Agent-Memory is distributed exclusively as an ES module and does not support CommonJS require(); CommonJS consumers must use a bundler with ESM interop or migrate to ES modules.
Both openclaw >=2026.3.7 and node-llama-cpp ^3.16.2 are declared as optional peer dependencies, so the package works standalone without either.[1] When OpenClaw integration is used, the compatibility floor for both the plugin API and the minimum gateway version is >=2026.3.13, as declared in the openclaw.compat field of package.json — see OpenClaw integration for full API details.[1] opik ^1.0.0 is an optional runtime dependency and is not required for core functionality.[1]
Three CLI binaries are shipped with the package — migrate-sqlite-to-tcvdb, export-tencent-vdb, and read-local-memory — each pointing to a corresponding file in ./bin/.[1]
The build script runs two steps in sequence: build:plugin (via tsdown) compiles the main plugin, then build:scripts compiles the three utility CLI scripts via tsc.[1] Tests are run with Vitest: npm test runs vitest run, npm run test:watch runs Vitest in watch mode, and npm run test:coverage runs vitest run --coverage.[1] Test source files (*.test.ts, *.spec.ts, and __tests__/ directories inside src/) are excluded from the published npm package via negation patterns in the files field.[1]
Sources