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	8859
title	Enforce ESM Worker Instantiation Globally
state	Closed
labels	bugaicore
assignees	tobiu
createdAt	Jan 22, 2026, 12:48 AM
updatedAt	Jan 22, 2026, 12:54 AM
githubUrl	https://github.com/neomjs/neo/issues/8859
author	tobiu
commentsCount	1
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Jan 22, 2026, 12:54 AM

Enforce ESM Worker Instantiation Globally

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

Closed v11.23.1 bugaicore

tobiu commented on Jan 22, 2026, 12:48 AM

The hasJsModules check in src/worker/Manager.mjs and src/main/addon/ServiceWorker.mjs incorrectly assumes that dist/development and dist/production do not support ES modules. This causes blank pages as the new webpack builds output ESM bundles.

Changes:

Update src/worker/Manager.mjs to always instantiate workers with {type: 'module'}.
Refactor hasJsModules logic to primarily control file extensions (.mjs vs .js) and pathing, rather than module capability.
Update src/main/addon/ServiceWorker.mjs similarly.
Review src/remotes/Api.mjs to ensure path resolution logic remains correct under the new environment assumptions.

tobiu added the bug label on Jan 22, 2026, 12:48 AM

tobiu added the ai label on Jan 22, 2026, 12:48 AM

tobiu added the core label on Jan 22, 2026, 12:48 AM

tobiu referenced in commit 72bdde6 - "fix: Enforce ESM worker instantiation for all environments (#8859)" on Jan 22, 2026, 12:54 AM

tobiu assigned to @tobiu on Jan 22, 2026, 12:54 AM

tobiu Jan 22, 2026, 12:54 AM

Input from Gemini 3 Pro:

✦ I have refactored src/worker/Manager.mjs, src/main/addon/ServiceWorker.mjs, and src/remotes/Api.mjs to enforce ESM worker instantiation across all environments.

Changes:

Renamed hasJsModules to useMjsFiles to correctly reflect its purpose (file extension/path selection vs. module capability).

Updated src/worker/Manager.mjs to always use {type: 'module'} when creating workers.

Updated src/main/addon/ServiceWorker.mjs to always use {type: 'module'} when registering the service worker.

Updated src/remotes/Api.mjs to use the renamed variable for consistency in path resolution.

This ensures that dist/development and dist/production builds, which are now ESM, are loaded correctly.

tobiu closed this issue on Jan 22, 2026, 12:54 AM