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	9547
title	Fix RemoteMethodAccess for Main Thread Addons and Instance-to-Instance ID collision
state	Closed
labels	bugaiarchitecturecore
assignees	tobiu
createdAt	Mar 24, 2026, 10:18 PM
updatedAt	Mar 24, 2026, 10:19 PM
githubUrl	https://github.com/neomjs/neo/issues/9547
author	tobiu
commentsCount	1
parentIssue	9449
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Mar 24, 2026, 10:19 PM

Fix RemoteMethodAccess for Main Thread Addons and Instance-to-Instance ID collision

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

Closed v12.1.0 bugaiarchitecturecore

tobiu commented on Mar 24, 2026, 10:18 PM

Bug Description

In PR #9546, we refactored RemoteMethodAccess to support declarative remote configs for instance IPC. This introduced two critical regressions:

Main thread addons (like Stylesheet) were no longer broadcasting registerRemote messages because the check in core/Base.mjs only checked me.singleton === true, failing to account for me.isMainThreadAddon === true. This caused errors like Cannot read properties of undefined (reading 'Stylesheet').
When the registerRemote message was received, onRegisterRemote was passing the entire message payload (which includes a message id generated by promiseMessage) to generateRemote. This caused generateRemote to mistake the message ID for the remote instance ID, leading to errors like Invalid remote instance id "neo-main-12".

Proposed Solution

Restore || me.isMainThreadAddon === true in src/core/Base.mjs inside initRemote.
Pass a sanitized object to generateRemote inside onRegisterRemote in src/worker/mixin/RemoteMethodAccess.mjs to prevent the message id from leaking.
Enhance the ID check in onRemoteMethod to fallback to Neo.idMap if the Neo.manager.Instance is not available yet.

tobiu added the bug label on Mar 24, 2026, 10:18 PM

tobiu added the ai label on Mar 24, 2026, 10:18 PM

tobiu added the architecture label on Mar 24, 2026, 10:18 PM

tobiu added the core label on Mar 24, 2026, 10:18 PM

tobiu referenced in commit b86088c - "fix(core): Resolve RemoteMethodAccess routing for main thread addons and instance IPC ID collisions (#9547)" on Mar 24, 2026, 10:18 PM

tobiu assigned to @tobiu on Mar 24, 2026, 10:18 PM

tobiu Mar 24, 2026, 10:19 PM

Input from Gemini 3.1 Pro:

✦ I have successfully resolved the routing issues within RemoteMethodAccess.

Root Cause Analysis:

The first error (Cannot read properties of undefined (reading 'Stylesheet')) occurred because core/Base.mjs was checking if (me.singleton === true) but omitted || me.isMainThreadAddon === true. Main thread addons act like singletons but use isMainThreadAddon: true. Because they were excluded, they fell back to the instance routing block and never broadcasted their existence to the App Worker.

The second error (Invalid remote instance id "neo-main-12") occurred because onRegisterRemote in src/worker/mixin/RemoteMethodAccess.mjs was passing the raw registerRemote message directly to generateRemote(remote). This raw message contains a message id appended by promiseMessage(). generateRemote incorrectly intercepted this message ID and assigned it as the remoteId proxy for the target.

Implementation Details:

Restored me.isMainThreadAddon === true inside src/core/Base.mjs's initRemote() to ensure addons broadcast correctly.

Sanitized the payload passed to generateRemote() inside onRegisterRemote() by only passing className and origin, preventing the promiseMessage ID from leaking into the remoteId parameter.

Enhanced the onRemoteMethod resolution logic to optionally fall back to Neo.idMap if the Instance manager is not yet available, ensuring robustness.

I will close this ticket.

tobiu added parent issue #9449 on Mar 24, 2026, 10:19 PM

tobiu closed this issue on Mar 24, 2026, 10:19 PM