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	9419
title	Implement Dynamic Module Loading in `Neo.worker.Data`
state	Closed
labels	enhancementaicore
assignees	tobiu
createdAt	Mar 9, 2026, 4:46 PM
updatedAt	Mar 12, 2026, 3:54 PM
githubUrl	https://github.com/neomjs/neo/issues/9419
author	tobiu
commentsCount	1
parentIssue	9449
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Mar 12, 2026, 3:54 PM

Implement Dynamic Module Loading in `Neo.worker.Data`

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

Closed v12.1.0 enhancementaicore

tobiu commented on Mar 9, 2026, 4:46 PM

Goal

Add a remote method access (RMA) endpoint to the Data Worker to dynamically import ES modules at runtime.

Context

To achieve a high-performance Connection -> Parser -> Normalizer pipeline inside the Data Worker, the Data Worker needs access to application-specific Parser and Normalizer classes. Instead of serializing complex mapping functions across thread boundaries, the App Worker will instruct the Data Worker to dynamically import() the necessary module files.

Architecture

Implement an async loadModule({path}) method in src/worker/Data.mjs (similar to the existing test helper in the App Worker).
Use await import(/* webpackIgnore: true */ path) to load the module natively.
Address Webpack production bundling strategies (e.g., magic comments or dynamic chunks) as needed during implementation.

tobiu added the enhancement label on Mar 9, 2026, 4:46 PM

tobiu added the ai label on Mar 9, 2026, 4:46 PM

tobiu added the core label on Mar 9, 2026, 4:46 PM

tobiu added parent issue #9404 on Mar 9, 2026, 4:46 PM

tobiu cross-referenced by #9420 on Mar 9, 2026, 4:46 PM

tobiu assigned to @tobiu on Mar 9, 2026, 4:47 PM

tobiu cross-referenced by #9449 on Mar 12, 2026, 3:20 PM

tobiu removed parent issue #9404 on Mar 12, 2026, 3:21 PM

tobiu added parent issue #9449 on Mar 12, 2026, 3:21 PM

tobiu referenced in commit 7830abe - "feat: Implement Dynamic Module Loading in Data Worker (#9419)" on Mar 12, 2026, 3:53 PM

tobiu Mar 12, 2026, 3:54 PM

Input from Gemini 3.1 Pro:

✦ I have successfully implemented dynamic module loading in Neo.worker.Data.

Changes Made

Added the remote config mapping to expose loadModule to the app worker.

Implemented async loadModule({path}) which utilizes Webpack's dynamic import() capabilities natively.

Integrated the specific webpackExclude rule /* webpackExclude: /(?:\/|\\)(dist|node_modules)\/(?!neo.mjs)/ */ to ensure robust bundler chunking and ignore irrelevant system folders.

Ran all unit tests (331) successfully.

Code has been committed and pushed under #9419.

tobiu closed this issue on Mar 12, 2026, 3:54 PM

Implement Dynamic Module Loading in Neo.worker.Data

Goal

Context

Architecture

Changes Made

Implement Dynamic Module Loading in `Neo.worker.Data`