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	9608
title	Fix Event Resolution and Parent Hierarchy Regressions in Nested Sub-Grids
state	Closed
labels	bugaigrid
assignees	tobiu
createdAt	Mar 31, 2026, 12:43 PM
updatedAt	Mar 31, 2026, 12:47 PM
githubUrl	https://github.com/neomjs/neo/issues/9608
author	tobiu
commentsCount	1
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Mar 31, 2026, 12:47 PM

Fix Event Resolution and Parent Hierarchy Regressions in Nested Sub-Grids

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

Closedbugaigrid

tobiu commented on Mar 31, 2026, 12:43 PM

When transitioning to the Multi-Body grid architecture, explicit parentId injections were removed from GridContainer.beforeSetBody and GridContainer.beforeSetHeaderToolbar to prevent parentage collisions against the newly introduced wrapper elements (bodyWrapper, headerWrapper).

However, this change prevents sub-components from correctly resolving their logical ancestors during early initialization (e.g., inside processConfigs), causing two specific regressions:

TypeError: Cannot read properties of undefined (reading 'apply'): Event bindings mapped via strings (e.g., listeners: { isScrollingChange: 'onGridIsScrollingChange' }) fail to resolve because getController() relies on traversing this.parent upwards. During early instantiation, this.parent is null, causing cb.fn to become undefined and throwing an exception upon event firing.
TypeError: Cannot read properties of null (reading 'id'): Inside src/grid/header/Toolbar.mjs, createSortZone unconditionally attempts to read me.parent.id for its boundaryContainerId mapping.

To resolve this, we will introduce resilient fallback routines by explicitly overriding getController() in Body.mjs and Toolbar.mjs to traverse this.gridContainer when this.parent is functionally unavailable, avoiding hard coupling to structural DOM relationships that are still parsing.

tobiu added the bug label on Mar 31, 2026, 12:43 PM

tobiu added the ai label on Mar 31, 2026, 12:43 PM

tobiu added the grid label on Mar 31, 2026, 12:43 PM

tobiu referenced in commit 5890988 - "fix: Restore native parentage resolution and prevent item null crashes (#9608)" on Mar 31, 2026, 12:46 PM

tobiu Mar 31, 2026, 12:47 PM

Input from Gemini 3.1 Pro (Antigravity):

✦ Resolved. The parent hierarchy now correctly maintains linkage natively because me.items is instantiated prior to the wrapper container snatching ownership of the child components. This correctly satisfies the Container.remove algorithm, allowing it to gracefully iterate empty items instead of crashing on a null iteration. Controller lookups correctly climb the object graph dynamically.

tobiu assigned to @tobiu on Mar 31, 2026, 12:47 PM

tobiu closed this issue on Mar 31, 2026, 12:47 PM