LearnNewsExamplesServices
Frontmatter
id9716
titleDisable SQLiteVectorManager boot when Engine is Chroma
stateClosed
labels
bugai
assigneestobiu
createdAtApr 5, 2026, 10:33 AM
updatedAtApr 5, 2026, 10:34 AM
githubUrlhttps://github.com/neomjs/neo/issues/9716
authortobiu
commentsCount1
parentIssuenull
subIssues[]
subIssuesCompleted0
subIssuesTotal0
blockedBy[]
blocking[]
closedAtApr 5, 2026, 10:34 AM

Disable SQLiteVectorManager boot when Engine is Chroma

Closedbugai
tobiu
tobiu commented on Apr 5, 2026, 10:33 AM

When memory-core/config.mjs sets the vector database engine strictly to 'chroma', the hybrid SQLiteVectorManager was still executing its initAsync routine. This caused it to reach out to the local LLM (TextEmbeddingService.embedText) to validate table dimensions during server startup, unintentionally turning on the Ollama instance or crashing if unavailable.

We need to add a strict opt-out within SQLiteVectorManager.initAsync so it immediately returns if the engine is not 'neo' or 'both'.

tobiu added the bug label on Apr 5, 2026, 10:33 AM
tobiu added the ai label on Apr 5, 2026, 10:33 AM
tobiu referenced in commit 8076d97 - "fix(memory-core): Opt out of SQLiteVectorManager initialization when engine is chroma (#9716)" on Apr 5, 2026, 10:34 AM
tobiu assigned to @tobiu on Apr 5, 2026, 10:34 AM
tobiu
tobiu Apr 5, 2026, 10:34 AM

Fixed: SQLiteVectorManager now returns early from initAsync if aiConfig.engine is configured as 'chroma', preventing unnecessary local LLM pings and avoiding zombie subprocesses.

tobiu closed this issue on Apr 5, 2026, 10:34 AM