What is the Neural Link?

The Neural Link is a bi-directional bridge that connects AI agents directly to the Neo.mjs runtime. It lets agents inspect the Scene Graph, component state, event listeners, computed styles, and DOM rectangles, and mutate the running application in real time.

Why is Neo.mjs called an Application Engine instead of a framework?

Neo.mjs maintains persistent application objects in a worker-backed Scene Graph instead of compiling application state away into ephemeral DOM nodes. That architecture enables multi-window orchestration, runtime permutation, and deep AI introspection.

What is Context Engineering?

Context Engineering shapes the information and tool environment around AI agents. Neo.mjs implements it through Knowledge Base, Memory Core, GitHub Workflow, and Neural Link MCP servers for frontier harnesses, plus a File System MCP server for internal Neo.ai.Agent local loops.

What is the Neo.mjs Agent OS?

The Neo.mjs Agent OS is the repository Brain: source code and services for Memory Core, Knowledge Base, Active Hybrid GraphRAG, DreamService, Golden Path synthesis, A2A coordination, and Neural Link tooling.

Frontmatter

id	10499
title	ChromaDB multiple operator query error in MemoryCore
state	Closed
labels	bugaicore
assignees	[]
createdAt	Apr 29, 2026, 5:42 PM
updatedAt	Apr 30, 2026, 12:55 PM
githubUrl	https://github.com/neomjs/neo/issues/10499
author	neo-gemini-pro
commentsCount	0
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Apr 30, 2026, 12:55 PM

ChromaDB multiple operator query error in MemoryCore

Closed v13.0.0/archive-v13-0-0-chunk-7 bugaicore

neo-gemini-pro commented on Apr 29, 2026, 5:42 PM

Context — The agent IDE encountered a ChromaDB error upon startup during a memory query: Expected 'where' to have exactly one operator, but got 2. This prevented historical session context from loading via the Memory Core.
The Problem — The issue stems from the recent multi-tenant isolation (#10000). When RequestContextService.getUserId() returned a valid tenant userId alongside an existing sessionId or category, the MemoryService and SummaryService constructed a where object with multiple keys (e.g., { sessionId: '...', userId: '...' }). ChromaDB requires explicit $and grouping for multiple query conditions.
The Architectural Reality — The bug resides in /ai/mcp/server/memory-core/services/MemoryService.mjs (in listMemories and queryMemories) and /ai/mcp/server/memory-core/services/SummaryService.mjs (in querySummaries).
The Fix — I modified the where clause construction logic to wrap multiple keys in an $and array (e.g., { $and: [{ sessionId }, { userId }] }).
Acceptance Criteria
- MemoryService.listMemories handles both single and multiple key filters without ChromaDB syntax errors.
- MemoryService.queryMemories handles both single and multiple key filters.
- SummaryService.querySummaries handles both single and multiple key filters.
Out of Scope — Structural changes to the underlying ChromaDB collections or multi-tenant schema beyond this specific query syntax fix.
Related — #10000
Origin Session ID: df8049d8-56ad-417b-ae0e-17a38e22a0ae

tobiu referenced in commit 206374e - "fix(memory-core): fix ChromaDB multiple operator bug with explicit $and clauses (#10499) (#10508) on Apr 30, 2026, 12:55 PM

tobiu closed this issue on Apr 30, 2026, 12:55 PM