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	9442
title	Fix Grid Pooling DOM thrashing and Collection internalId lookup
state	Closed
labels	bugaicoregrid
assignees	tobiu
createdAt	Mar 11, 2026, 2:27 PM
updatedAt	Mar 11, 2026, 3:30 PM
githubUrl	https://github.com/neomjs/neo/issues/9442
author	tobiu
commentsCount	1
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Mar 11, 2026, 3:30 PM

Fix Grid Pooling DOM thrashing and Collection internalId lookup

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

Closed v12.1.0 bugaicoregrid

tobiu commented on Mar 11, 2026, 2:27 PM

Goal

Stabilize unit tests by addressing grid pooling DOM thrashing, fixing a cell recycling TypeError, and improving internalId support in collection lookups.

Issues Addressed

Grid Pooling (src/grid/Body.mjs): Prevented cellPoolSize from shrinking during regular horizontal scrolling unless forced, preventing unnecessary DOM cell removal and recreation (DOM thrashing). This fixes the Pooling.spec.mjs tests.
Cell Recycling (src/grid/Row.mjs): Added optional chaining (node?.data?.field) when mapping existing cells to prevent a TypeError: Cannot read properties of null when a node has no data. This fixes the GridScrollProfile.spec.mjs test.
Collection Lookups (src/collection/Base.mjs): Simplified indexOf and indexOfKey to use the internal this.get(key) method. This makes the code cleaner and inherently adds internalId support to index lookups, paving the way for fixing the GalleryInternalId tests.

tobiu added the bug label on Mar 11, 2026, 2:27 PM

tobiu added the ai label on Mar 11, 2026, 2:27 PM

tobiu added the core label on Mar 11, 2026, 2:27 PM

tobiu added the grid label on Mar 11, 2026, 2:27 PM

tobiu referenced in commit 07f6da0 - "fix(grid): Prevent DOM thrashing and stabilize tests (#9442)" on Mar 11, 2026, 2:28 PM

tobiu Mar 11, 2026, 2:28 PM

Input from Gemini 3.1 Pro:

✦ I have applied the following fixes to stabilize the tests:

src/grid/Body.mjs: Prevented shrinking of cellPoolSize during horizontal scrolling, which eliminates the DOM thrashing seen in Pooling.spec.mjs.

src/grid/Row.mjs: Added optional chaining (node?.data?.field) to prevent a TypeError in GridScrollProfile.spec.mjs during cell recycling.

src/collection/Base.mjs: Cleaned up indexOf and indexOfKey to use this.get(key). This resolves the internalId lookup issues.

The tests have improved, though GalleryInternalId.spec.mjs is still failing due to other problems with Gallery's selection model which we are investigating next.

tobiu referenced in commit a48d756 - "fix(data): Preserve internalId in RecordFactory (#9442)" on Mar 11, 2026, 2:59 PM

tobiu closed this issue on Mar 11, 2026, 3:30 PM

tobiu assigned to @tobiu on Mar 11, 2026, 3:30 PM