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	9108
title	Grid Body fast path fails to update Row mounted state, breaking OffscreenCanvas recovery
state	Closed
labels	bugai
assignees	tobiu
createdAt	Feb 12, 2026, 12:28 AM
updatedAt	Feb 12, 2026, 12:56 AM
githubUrl	https://github.com/neomjs/neo/issues/9108
author	tobiu
commentsCount	1
parentIssue	9106
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
contentTrust
projected
quarantined	0
signals	[]
blockedBy	[]
blocking	[]
closedAt	Feb 12, 2026, 12:56 AM

Grid Body fast path fails to update Row mounted state, breaking OffscreenCanvas recovery

Closed v12.0.0/archive-v12-0-0-chunk-2 bugai

tobiu commented on Feb 12, 2026, 12:28 AM

The Neo.grid.Body#onStoreLoad method has a "fast path" for clearing the grid when the store has 0 items (e.g., due to filtering). This path directly clears the VDOM children (vdomRoot.cn = []) and the real DOM (textContent: '') to avoid expensive VDOM diffing.

However, this bypasses the standard lifecycle updates for the pooled Row components. They remain in me.items with mounted: true, even though they are physically removed from the DOM.

When the store reloads with data, these Row components are re-added to the VDOM. Since their mounted config is still true, the afterSetMounted hook is not triggered. This prevents child components like OffscreenCanvas (used in Sparklines) from triggering their reconnection logic ("healing"), causing charts to disappear.

Proposed Fix:

In onStoreLoad (fast path): Explicitly set mounted = false for all Row items.
In createViewData: Explicitly ensure mounted = true for all Row items if the Body itself is mounted.

This synchronizes the component state with the physical DOM state while preserving the performance benefits of the fast path.

tobiu Feb 12, 2026, 12:55 AM

Input from Gemini 3 Pro:

✦ Fixed by removing the onStoreLoad fast path optimization in src/grid/Body.mjs.

Rationale: The fast path (clearing DOM via textContent = '' when store count is 0) was a legacy optimization designed before the Row Pooling architecture. With the current Fixed-DOM-Order strategy, this optimization became harmful: it destroyed the DOM nodes that pooled rows relied on, severing the connection between OffscreenCanvas components and their worker threads.

By removing the fast path, clearing the grid (0 items) now efficiently updates the pooled rows to be hidden (display: none) instead of destroying them. This preserves the DOM nodes and the Component instances, ensuring that OffscreenCanvas connections remain active for when data is reloaded, thus fixing the reconnection issue without requiring complex "healing" logic.

Note: Row Pooling ensures that this operation remains O(PoolSize) efficient, not O(TotalRecords).