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	8497
title	ServiceWorker: Implement Remote Method Broadcast and Replay for Multi-Client Support
state	Closed
labels	bugaicore
assignees	tobiu
createdAt	Jan 10, 2026, 12:28 PM
updatedAt	Jan 10, 2026, 12:36 PM
githubUrl	https://github.com/neomjs/neo/issues/8497
author	tobiu
commentsCount	1
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Jan 10, 2026, 12:36 PM

ServiceWorker: Implement Remote Method Broadcast and Replay for Multi-Client Support

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

Closed v11.20.0 bugaicore

tobiu commented on Jan 10, 2026, 12:28 PM

The Service Worker does not properly propagate remote method registration to multiple connected clients (App Workers) or handle new connections after initialization.

The Problem:

Multi-Client Support: Neo.core.Base.promiseRemotes targets 'app', but in a Service Worker context, 'app' represents any connected client. The current logic attempts to send to a single port, missing others.
Future Clients: initRemote runs once on startup. Clients connecting after startup (e.g., opening a new tab) never receive the registerRemote message and cannot access Service Worker methods.
Initialization Crash: promiseRemotes fails if called when no clients are connected (because sendMessage returns null), rejecting the initialization promise.

Proposed Solution: Adopt the "Registry & Replay" pattern used for SharedWorkers (#8339).

src/core/Base.mjs (initRemote):
- Detect Neo.workerId === 'service'.
- Store remote.app definitions in Neo.currentWorker.remotesToRegister.
src/worker/ServiceBase.mjs:
- Add remotesToRegister = [].
- Update createMessageChannel (triggered by onConnect) to iterate remotesToRegister and send registerRemote to the new client's port.
- Refine hasWorker('app') to return true only if active ports exist, preventing promiseRemotes from failing when no clients are connected.

This ensures every client—existing or new—receives the remote method definitions.

tobiu added the bug label on Jan 10, 2026, 12:28 PM

tobiu added the ai label on Jan 10, 2026, 12:28 PM

tobiu added the core label on Jan 10, 2026, 12:28 PM

tobiu assigned to @tobiu on Jan 10, 2026, 12:28 PM

tobiu referenced in commit 37a786f - "fix: Implement Service Worker remote method broadcast and replay (#8497)" on Jan 10, 2026, 12:35 PM

tobiu Jan 10, 2026, 12:36 PM

Input from tobiu:

◆ Implemented the "Registry & Replay" pattern for Service Worker remote method registration.

Changes:

src/core/Base.mjs (initRemote):

Added detection for Neo.workerId === 'service'.

Now populates Neo.currentWorker.remotesToRegister with remote.app definitions instead of relying solely on promiseRemotes immediate execution.

src/worker/ServiceBase.mjs:

Added remotesToRegister array.

Updated createMessageChannel to iterate through remotesToRegister and post registerRemote messages to the newly connected port. This ensures every connecting client (tab) receives the remote method proxies.

Refined hasWorker(name) to strict mode (!!this.getPort(name) || !!this.lastClient), removing the hardcoded name === 'app' check. This prevents promiseRemotes from falsely attempting to send messages when no clients are actually connected, preventing initialization errors.

This ensures robust remote method availability across all connected windows and tabs.

tobiu closed this issue on Jan 10, 2026, 12:36 PM