Skip to content
This repository was archived by the owner on Jun 23, 2026. It is now read-only.

v0.5.3 — PM2 auto-start + OpenAI embedding default

Choose a tag to compare

@VKirill VKirill released this 17 May 14:02
· 13 commits to main since this release

TL;DR

  • install.sh now auto-starts the PM2 scheduler — no manual pm2 start step.
  • Default embedding is now OpenAI text-embedding-3-large @ 1024-d (was Voyage AI voyage-3-lite @ 512-d). Voyage remains supported via config + VOYAGE_API_KEY fallback.
  • Breaking: vector schema is now 1024-d. Existing vectors.db must be archived and recreated.
  • Breaking: new installs require OPENAI_API_KEY in ~/.claude/claude-mem.env.

Upgrade from 0.5.2

# 1. Reinstall the package
npm i -g github:VKirill/TencentDB-Memory-Claude-Code#v0.5.3

# 2. Add OpenAI key to env file
echo 'OPENAI_API_KEY=sk-...' >> ~/.claude/claude-mem.env
chmod 600 ~/.claude/claude-mem.env

# 3. Stop scheduler + archive old vectors.db in each project + re-run install
pm2 stop tencentdb-memory-scheduler
for p in $(grep -v '^#' ~/.claude/claude-mem-projects.txt | grep -v '^$'); do
  mv "$p/.claude/memory/vectors.db" "$p/.claude/memory/vectors.db.bak.0.5.2" 2>/dev/null
done

# 4. Re-run install.sh — it will detect pm2 + start the scheduler automatically
bash "$(npm root -g)/@vkirill/tencentdb-memory-claude-code/claude-code-integration/install.sh"

The scheduler will recreate vectors.db per project on the next tick with the new 1024-d schema.

Fresh install

Follow INSTALL.md — same steps as before, but the API key you need is OpenAI now (signup at https://platform.openai.com/api-keys), not Voyage.

Changes

Added

  • install.sh auto-starts the PM2 scheduler when pm2 is on PATH. Idempotent — skips if tencentdb-memory-scheduler already running. Error-tolerant — pm2 failures don't abort install. Retains print-instructions fallback for systems without pm2. (5b7fa55)

Changed

  • Default embedding provider switched from Voyage AI to OpenAI. The codebase abstraction is OpenAI-compatible HTTP; Voyage's API rejected the dimensions parameter (Voyage expects output_dimension), causing all L1 facts to be stored metadata-only with semantic recall inert. Switching default to OpenAI eliminates this mismatch and unlocks vector search by default. (b89f26a)
  • Default model is text-embedding-3-large @ 1024-d. Cost: $0.13 per 1M tokens — negligible at hobbyist volume; text-embedding-3-small documented as cheaper alternative. (ab138b7)
  • MCP server version is read dynamically from package.json instead of hardcoded. (5b7fa55)
  • .gitignore extended with a secrets safety-net section.

Breaking

  • Vector schema: 512-d → 1024-d. Existing l1_vec / l0_vec columns will reject 1024-d writes. Migration: stop scheduler → archive vectors.db → restart.
  • Required env var: OPENAI_API_KEY. Falls back to VOYAGE_API_KEY if user keeps Voyage in their config.json.