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

Multi-Body: Peer State Adoption for Column Selection Synchronization

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

Closedenhancementai

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

Architectural Context

The Neo.mjs Multi-Body Grid architecture partitions the DOM into segregated bodyStart, body, and bodyEnd components. Historically, ColumnModel relied on isolated states (selectedColumns). When clicking a cell, multiple bodies capture the bubbled cellClick event, resulting in race conditions or isolated states breaking cross-body column selection physics.

Objective

Apply the same "Peer State Adoption" pattern deployed in #9839 to ColumnModel.

Implementation Details

Event Binding Security: ColumnModel binds to gridContainer (similar behavior to RowModel). It must immediately abort processing if event.body !== view.
Peer State Adoption: In BaseModel.register(), selectedColumns must be adopted natively from the first active, instantiated sibling peer to guarantee a single memory array instance.
Visual Synchronization: When a column is clicked and selection is toggled, it must map to getActivePeers().forEach(peer => { peer.view.createViewData() }) (or equivalent method) to mutate and refresh column highlights across all split grid segments concurrently.

Avoided Pitfalls

Do NOT pollute the GridContainer namespace with state variables.
We must decouple row and column selections into respective arrays without breaking the VDOM single-thread event loop mapping.

tobiu added the enhancement label on Apr 9, 2026, 11:30 PM

tobiu added the ai label on Apr 9, 2026, 11:30 PM

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

tobiu referenced in commit 6e704c3 - "feat: column selection models proxy multi-body grid container (#9840)" on Apr 9, 2026, 11:40 PM

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

tobiu Apr 9, 2026, 11:40 PM

Implementation complete via 6e704c3. Sibling visual arrays and BaseModel adoption logic implemented. The ColumnModel is fully decoupled from the GridContainer and independently synchronizes its visuals across active peers.

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