Frontmatter
| id | 9716 |
| title | Disable SQLiteVectorManager boot when Engine is Chroma |
| state | Closed |
| labels | bugai |
| assignees | tobiu |
| createdAt | Apr 5, 2026, 10:33 AM |
| updatedAt | Apr 5, 2026, 10:34 AM |
| githubUrl | https://github.com/neomjs/neo/issues/9716 |
| author | tobiu |
| commentsCount | 1 |
| parentIssue | null |
| subIssues | [] |
| subIssuesCompleted | 0 |
| subIssuesTotal | 0 |
| blockedBy | [] |
| blocking | [] |
| closedAt | Apr 5, 2026, 10:34 AM |
Disable SQLiteVectorManager boot when Engine is Chroma
Closedbugai
tobiu assigned to @tobiu on Apr 5, 2026, 10:34 AM

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
When
memory-core/config.mjssets the vector databaseenginestrictly to'chroma', the hybridSQLiteVectorManagerwas still executing itsinitAsyncroutine. 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.initAsyncso it immediately returns if the engine is not'neo'or'both'.