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	9478
title	Grid ScrollManager: Support dynamic windowId changes for Main Thread Addon registration
state	Closed
labels	bugaigrid
assignees	tobiu
createdAt	Mar 15, 2026, 2:59 PM
updatedAt	Mar 15, 2026, 3:06 PM
githubUrl	https://github.com/neomjs/neo/issues/9478
author	tobiu
commentsCount	1
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Mar 15, 2026, 3:06 PM

Grid ScrollManager: Support dynamic windowId changes for Main Thread Addon registration

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

Closed v12.1.0 bugaigrid

tobiu commented on Mar 15, 2026, 2:59 PM

The ScrollManager for the Neo.grid.Container currently determines the windowId for registering Main Thread Addons (like GridDragScroll and GridRowScrollPinning) by reading it directly from its assigned gridContainer inside the addon update methods.

However, in a multi-window architecture, if a grid component is moved from one browser window to another, the windowId of the grid changes dynamically. Because ScrollManager extends Neo.core.Base and is instantiated once, simply reading the container's windowId on-the-fly or ignoring its dynamic updates means the addons won't be properly unregistered from the old window and registered in the new window.

To fix this and ensure full multi-window support:

Introduce a windowId_ reactive config in ScrollManager.
Implement an afterSetWindowId(value, oldValue) hook. If oldValue is truthy (meaning a dynamic move happened), it should trigger a re-registration of the active addons.
Update Neo.grid.Container to pass its windowId into the ScrollManager config during onConstructed().
Update Neo.grid.Container's afterSetWindowId method to explicitly set the new windowId onto its scrollManager instance when a window move occurs.

tobiu added the bug label on Mar 15, 2026, 3:00 PM

tobiu added the ai label on Mar 15, 2026, 3:00 PM

tobiu added the grid label on Mar 15, 2026, 3:00 PM

tobiu referenced in commit c1a4056 - "Grid ScrollManager: Support dynamic windowId changes for Main Thread Addon registration (#9478)" on Mar 15, 2026, 3:06 PM

tobiu Mar 15, 2026, 3:06 PM

Input from Gemini 3.1 Pro:

✦ I have implemented the requested changes:

Introduced windowId_ (String|null) to Neo.grid.ScrollManager.

Implemented afterSetWindowId to correctly unregister old addons and register new ones when the windowId changes dynamically.

Updated Neo.grid.Container to pass the initial windowId and properly proxy dynamic windowId changes to the scrollManager.

Fixed the formatting to use let me = this; per the standard.

The changes have been committed and pushed to the repository. I will now close the issue.

tobiu assigned to @tobiu on Mar 15, 2026, 3:06 PM

tobiu closed this issue on Mar 15, 2026, 3:06 PM