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	9839
title	Multi-Body: Peer State Adoption for Row Selection Synchronization
state	Closed
labels	[]
assignees	tobiu
createdAt	Apr 9, 2026, 11:18 PM
updatedAt	Apr 9, 2026, 11:20 PM
githubUrl	https://github.com/neomjs/neo/issues/9839
author	tobiu
commentsCount	1
parentIssue	9492
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Apr 9, 2026, 11:20 PM

Multi-Body: Peer State Adoption for Row Selection Synchronization

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

Closed[]

tobiu commented on Apr 9, 2026, 11:18 PM

Context

Phase 6 of the Multi-Body Epic (#9486) involves adapting Selection Models for Split Rows. As identified in parent Epic #9492, the selection models (RowModel, CellModel) need to maintain cross-body synchronization.

Initially, delegating selection state arrays (selectedRows) upward to the GridContainer was considered. However, this causes severe namespace pollution, forcing the GridContainer to orchestrate internal states of independent Selection Model plugins.

Architecture: Peer State Adoption

To maintain encapsulation, we will implement the Peer State Adoption pattern in Neo.selection.grid.BaseModel and RowModel:

Zero GridContainer Pollution: The state arrays remain strictly inside the Selection Models.
Shared State Reference: During register(), a Selection Model will inspect its GridContainer for already instantiated sibling SMs. If a peer exists (e.g., body.selectionModel), the new SM adopts the peer's selectedRows array by reference. This establishes a single state truth across all sub-grid bodies natively via memory pointers.
Cross-Body VDOM Sync: RowModel will bind to gridContainer DOM events. When onRowClick fires, it mutates the shared Array and iteratively invokes updateRows() on all peers, forcing all active bodies (start, center, end) to physically update their neo-selected styling in unison.

Implementation Steps

Refactor Neo.selection.grid.BaseModel to adopt peer arrays.
Refactor Neo.selection.grid.RowModel to sync logical VDOM mutations.

tobiu added parent issue #9492 on Apr 9, 2026, 11:18 PM

tobiu referenced in commit 1161a17 - "feat: Implement Peer State Adoption for Grid Multi-Body Row Selection (#9839)" on Apr 9, 2026, 11:19 PM

tobiu assigned to @tobiu on Apr 9, 2026, 11:19 PM

tobiu Apr 9, 2026, 11:19 PM

Input from Antigravity (Gemini 3.1 Pro):

✦ Closed via commit 1161a17ae.

Resolution: Safely implemented the Peer State Adoption architecture on RowModel and BaseModel.

The Neo.selection.grid.BaseModel implements getActivePeers() to fetch instantiated sibling states isolated within the GridContainer.

RowModel seamlessly adopts the selectedRows array reference on module registration to share true memory points globally across peers.

Click events correctly bubble inside isolated active-peer nodes, forcing parallel grid visuals synchronously via native VDOM manipulations without grid pollution.

tobiu closed this issue on Apr 9, 2026, 11:20 PM