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	8998
title	Fix Grid Cell Selection for Pooled Cells
state	Closed
labels	bugairegression
assignees	tobiu
createdAt	Feb 5, 2026, 10:55 AM
updatedAt	Feb 5, 2026, 11:27 AM
githubUrl	https://github.com/neomjs/neo/issues/8998
author	tobiu
commentsCount	1
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Feb 5, 2026, 11:27 AM

Fix Grid Cell Selection for Pooled Cells

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

Closed v12.0.0 bugairegression

tobiu commented on Feb 5, 2026, 10:55 AM

The implementation of Hybrid Cell Pooling (#8992) broke cell-based selection models because Neo.grid.Body#getCellId returns transient "pooled" IDs (e.g., ...__cell-4) instead of stable "logical" IDs (e.g., ...__firstname). CellModel relies on stable IDs for state persistence and navigation.

Tasks:

Update Neo.grid.Body#getCellId to always return the logical ID (rowId__dataField).
Update Neo.grid.Body#getDataField to correctly resolve dataField from pooled cell IDs using mountedColumns.
Update Neo.grid.Row#applyRendererOutput to use the logical ID for selection state checks (selectedCells.includes(logicalId)), while preserving the pooled ID for the DOM attribute.

tobiu added the bug label on Feb 5, 2026, 10:55 AM

tobiu added the ai label on Feb 5, 2026, 10:55 AM

tobiu added the regression label on Feb 5, 2026, 10:55 AM

tobiu assigned to @tobiu on Feb 5, 2026, 11:24 AM

tobiu Feb 5, 2026, 11:25 AM

Input from Gemini 3 Pro:

✦ I have fixed the "JS errors on key nav" by updating Neo.grid.Body#getDataField to correctly handle pooled cell IDs.

The Fix: When a cell is pooled, its ID follows the format ...__cell-X. The previous implementation of getDataField naively extracted cell-X as the dataField, causing getCellId (and subsequently getColumn) to crash when looking up this invalid field name during navigation logic.

The updated getDataField now:

Detects pooled IDs (__cell-).

Extracts the pool index.

Iterates through the mountedColumns to find the matching column based on columnIndex % cellPoolSize.

Returns the correct dataField (e.g., lastname) instead of cell-X.

This ensures that CellModel can correctly resolve the current selection context during keyboard navigation, eliminating the crash. I reverted all other attempted architectural changes to getCellId and CellModel, preserving the strict separation of concerns and the performance benefits of the pooling implementation.

tobiu referenced in commit b4435df - "fix: Update GridBody.getDataField to resolve pooled cell IDs correctly (#8998)" on Feb 5, 2026, 11:25 AM

tobiu closed this issue on Feb 5, 2026, 11:27 AM