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	8339
title	Remote Method Registration Missing for Secondary Windows in SharedWorker
state	Closed
labels	bugaicore
assignees	tobiu
createdAt	Jan 5, 2026, 9:03 PM
updatedAt	Jan 5, 2026, 9:27 PM
githubUrl	https://github.com/neomjs/neo/issues/8339
author	tobiu
commentsCount	1
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Jan 5, 2026, 9:27 PM

Remote Method Registration Missing for Secondary Windows in SharedWorker

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

Closed v11.18.0 bugaicore

tobiu commented on Jan 5, 2026, 9:03 PM

Context: In a useSharedWorkers: true environment, a single worker instance (e.g., App, Data) serves multiple connected browser windows (Main Threads).

The Problem: Currently, Neo.core.Base#initRemote() sends the registerRemote message only once when the singleton is first initialized.

Window 1 Connects: Worker starts -> Singleton created -> initRemote called -> registerRemote sent to Window 1. Correct.
Window 2 Connects: Worker is already running -> Singleton already exists -> initRemote is NOT called again.
Result: Window 2 never receives the registerRemote handshake. It has no proxies for the singleton's remote methods.

Impact:

Any singleton remote method calls from secondary windows will fail.
Critical for Multi-Window Apps (Infinite Canvas, Portal, SharedCovid).

Proposed Solution:

State Persistence: In Neo.core.Base#initRemote, if target === 'main' and we are in a SharedWorker, store the registration payload (className, methods) in a registry on Neo.currentWorker (e.g., remoteMethodRegistry).
Replication: In Neo.worker.Base#onConnected (which fires every time a new window connects), iterate through this registry and re-send all stored registerRemote messages to the newly connected port only.

Scope:

src/core/Base.mjs: Update initRemote to register payloads.
src/worker/Base.mjs: Add registry storage and update onConnected to replay them.

tobiu added the bug label on Jan 5, 2026, 9:03 PM

tobiu added the ai label on Jan 5, 2026, 9:03 PM

tobiu added the core label on Jan 5, 2026, 9:03 PM

tobiu assigned to @tobiu on Jan 5, 2026, 9:03 PM

tobiu referenced in commit c3a4e13 - "Remote Method Registration Missing for Secondary Windows in SharedWorker #8339" on Jan 5, 2026, 9:26 PM

tobiu Jan 5, 2026, 9:27 PM

Input from Gemini 3 Pro:

✦ I have implemented the fix for remote method registration in SharedWorker environments.

Key Changes:

State Persistence (src/worker/Base.mjs):

Added remotesToRegister array to Neo.worker.Base.

In onConnected, the worker now iterates through this array and sends registerRemote messages to the newly connected port. This ensures that every new window receives the necessary proxy definitions.

Registration Logic (src/core/Base.mjs):

Updated initRemote to populate Neo.currentWorker.remotesToRegister when running in a SharedWorker environment.

Refactored the connection logic to be more robust: it now unconditionally registers the remote (if applicable) and then awaits the connected event if the worker is not yet ready, before proceeding to promiseRemotes.

Verification:

Verified that multi-window applications now correctly receive remote method proxies in secondary windows.

Confirmed that existing Dedicated Worker workflows and tests remain unaffected.

tobiu closed this issue on Jan 5, 2026, 9:27 PM

tobiu cross-referenced by #8497 on Jan 10, 2026, 12:28 PM