What is the 'Neural Link'?

The Neural Link is a bi-directional bridge that connects AI agents (like Gemini or Claude) directly to the Neo.mjs runtime. It allows agents to 'see' the application's Scene Graph, inspect component state, verify event listeners, and even mutate the running application in real-time. This turns the application into a 'glass box' for AI, enabling autonomous debugging and feature development.

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

Traditional frameworks are general-purpose libraries (like a Toyota) that help you organize code, but they compile away into ephemeral DOM nodes. Neo.mjs is a precision-engineered runtime (like an F1 car), similar to Unreal Engine for games. It maintains a persistent 'Scene Graph' of objects in a separate worker thread. These objects retain their identity, state, and relationships, allowing for advanced capabilities like multi-window orchestration, runtime permutation, and deep AI introspection that are impossible with 'melted plastic' DOM-based frameworks.

What is 'Context Engineering'?

Context Engineering is the practice of curating the environment and information flow for AI agents to maximize their autonomy. In Neo.mjs, this is implemented via three Model Context Protocol (MCP) servers: a Knowledge Base for semantic code understanding, a Memory Core for learning from past sessions, and a GitHub Workflow server for project management. This ecosystem allows agents to work as fully integrated members of the development team.

What is 'Object Permanence' in the context of Neo.mjs?

In Neo.mjs, UI components are persistent JavaScript objects living in the App Worker, not just transient rendering results. This 'Object Permanence' means a component (like a Dashboard) maintains its state (scroll position, user input, internal logic) even if it is detached from the DOM or moved to a different browser window. This is the 'Lego Technic' approach versus the 'Duplo' approach of traditional frameworks.

What is an 'Agent Operating System'?

Neo.mjs v11 introduced the concept of an Agent OS, where the platform itself provides the tools and interfaces for AI agents to operate. It combines a standalone, type-safe AI SDK for autonomous 'Code Execution' with the Neural Link for runtime control. This enables agents to monitor, debug, and heal the application autonomously, effectively acting as an operating system for synthetic intelligence.

How does Neo.mjs handle multi-window applications?

Neo.mjs uses shared web workers to run a single application instance across multiple browser windows. All windows share the same application state and data in real-time. Components can even move between windows while retaining their JavaScript instances. This enables desktop-class experiences like multi-window IDEs, browser-based email clients, and multi-screen control rooms.

What makes Neo.mjs different from React, Angular, or Vue?

Neo.mjs is fundamentally different in its architecture: (1) It uses True Multithreading via web workers to prevent UI jank, (2) It is an AI-Native Application Engine with built-in bridges for AI collaboration, and (3) It treats components as persistent objects in a Scene Graph, enabling native multi-window support and runtime permutation.

Frontmatter

id	9002
title	Fix Grid Row Cell Pooling Move Operations (Regression)
state	Closed
labels	bugregressionperformance
assignees	tobiu
createdAt	Feb 5, 2026, 12:18 PM
updatedAt	Feb 5, 2026, 12:47 PM
githubUrl	https://github.com/neomjs/neo/issues/9002
author	tobiu
commentsCount	1
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Feb 5, 2026, 12:47 PM

Fix Grid Row Cell Pooling Move Operations (Regression)

Name: Neo.mjs Application Engine
Author: Neo.mjs

Closed v12.0.0 bugregressionperformance

tobiu commented on Feb 5, 2026, 12:18 PM

We are observing a regression in Neo.grid.Row where horizontal scrolling triggers massive moveNode operations for pooled cells.

Symptoms:

The VDOM engine reports hundreds of moveNode deltas during horizontal scrolling.
This defeats the purpose of cell pooling (O(1) stability).

Root Cause: Recent fixes for Cell Selection Models likely reintroduced dependency on visual order for DOM ID generation or structure, causing the VDOM diff engine to see "reordered" nodes instead of stable, attribute-updated nodes.

Proposed Solution:

Strict Separation: Ensure DOM IDs for pooled cells are strictly index-based (...__cell-0, ...__cell-1) and never change order in the vdom.cn array.
Dataset Identifier: Use a data-cell-id attribute for the logical identifier needed by Selection Models, instead of relying on the DOM ID.
Refactor Selection Model: Update CellModel to query by data-cell-id (or mapped logical ID) rather than DOM ID.

This prioritizes scrolling performance (Zero GC/Layout Thrashing) over Selection Model lookups.

tobiu added the bug label on Feb 5, 2026, 12:18 PM

tobiu added the regression label on Feb 5, 2026, 12:18 PM

tobiu added the performance label on Feb 5, 2026, 12:18 PM

tobiu assigned to @tobiu on Feb 5, 2026, 12:19 PM

tobiu referenced in commit 7e7091f - "fix: Implement Full Pool Rendering in Grid Row for zero structure deltas (#9002)" on Feb 5, 2026, 12:45 PM

tobiu Feb 5, 2026, 12:46 PM

Input from Gemini 3 Pro:

✦ I have implemented the "Full Pool Rendering" strategy.

Implementation Details:

Stable VDOM Structure: Neo.grid.Row#createVdom now renders the entire cellPoolSize range of pooled cells in every pass.

Placeholders: If a pool index is not currently required by a mounted column, a placeholder cell (hidden) is rendered in that slot.

Logical IDs: Added ds: { cellId: ... } to all cells to support Selection Models via dataset attributes instead of DOM IDs.

Result: Horizontal scrolling now generates zero insertNode, removeNode, or moveNode operations for the pooled cells. All updates are efficient attribute changes (style, cls, innerHTML), restoring the intended O(1) performance of the cell pooling feature.

tobiu closed this issue on Feb 5, 2026, 12:47 PM