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	9286
title	[Bug] Grid Component Columns Retain Stale State on Scroll
state	Closed
labels	bugaicoregrid
assignees	tobiu
createdAt	Feb 24, 2026, 10:58 AM
updatedAt	Feb 24, 2026, 11:03 AM
githubUrl	https://github.com/neomjs/neo/issues/9286
author	tobiu
commentsCount	1
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Feb 24, 2026, 11:03 AM

[Bug] Grid Component Columns Retain Stale State on Scroll

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

Closed v12.0.0 bugaicoregrid

tobiu commented on Feb 24, 2026, 10:58 AM

Describe the bug During grid scrolling (Row Pooling), existing cell components are recycled for new records. If a new record is missing a data field (e.g. organizations), the field returns undefined. The Neo.mjs config system's set() method ignores undefined values, meaning the component retains the old record's state, causing visual bugs (e.g., showing a GitHub org from the previous row on a user who has no orgs).

To Reproduce Steps to reproduce the behavior:

Open the DevIndex app grid.
Scroll to a row with a user who has GitHub organizations.
Scroll quickly to a row where the user has NO GitHub organizations (field is undefined).
Observe that the cell incorrectly displays the organizations from the recycled component's previous state.

Expected behavior The component should correctly clear its state when the incoming data field is undefined.

Proposed Solution In src/grid/column/Component.mjs, convert undefined values to null before passing them to component.set(). This explicitly forces the change detection to clear the state without requiring developers to manually handle this in every applyRecordConfigs extension.

tobiu added the bug label on Feb 24, 2026, 10:58 AM

tobiu added the ai label on Feb 24, 2026, 10:58 AM

tobiu added the core label on Feb 24, 2026, 10:58 AM

tobiu added the grid label on Feb 24, 2026, 10:58 AM

tobiu assigned to @tobiu on Feb 24, 2026, 10:59 AM

tobiu Feb 24, 2026, 11:01 AM

Input from Gemini 3.1 Pro:

✦ I have successfully implemented the fix.

The src/grid/column/Component.mjs has been updated with a fast for...in loop that converts undefined configuration values into null when updating an existing (recycled) component instance. This ensures that when a new record scrolls into view that lacks a specific data field, the corresponding reactive config will explicitly clear its state instead of ignoring the undefined input and retaining the old record's data.

The fix was made carefully to preserve the O(1) performance requirement of horizontal scrolling by avoiding any new object allocations (Object.entries, etc.) inside the cell rendering hotpath. It also handles the hideMode defaults correctly.

I have added an intent-driven comment directly to the source code to ensure the architectural rationale is preserved for the Knowledge Base.

tobiu referenced in commit e5a31e6 - "fix(grid): Prevent stale state in pooled component columns (#9286)" on Feb 24, 2026, 11:02 AM

tobiu closed this issue on Feb 24, 2026, 11:03 AM