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	8948
title	Epic: Dynamic Worker Architecture & Import Protocol
state	Closed
labels	epicdeveloper-experienceaiarchitecture
assignees	tobiu
createdAt	Feb 2, 2026, 2:59 PM
updatedAt	Feb 2, 2026, 11:54 PM
githubUrl	https://github.com/neomjs/neo/issues/8948
author	tobiu
commentsCount	1
parentIssue	null
subIssues	8949 Feat: `Manager.startWorker` Remote Method 8950 Refactor: Move `loadModule` to `Neo.worker.Base` 8951 Feat: Smart Initialization for SparklineComponent 8952 Bug: Dynamic Worker Start triggers Double App Init & Canvas Race Condition 8953 Feat: Optional Canvas Worker Entry Point (`useCanvasWorkerStartingPoint`) 8954 Feat: Generic Sparkline Component & Grid Column 8955 Feat: Migrate Sparkline Renderer to `src/canvas` & Enforce Defaults
subIssuesCompleted	7
subIssuesTotal	7
blockedBy	[]
blocking	[]
closedAt	Feb 2, 2026, 11:54 PM

Epic: Dynamic Worker Architecture & Import Protocol

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

Closed v12.0.0 epicdeveloper-experienceaiarchitecture

tobiu commented on Feb 2, 2026, 2:59 PM

This epic covers the implementation of a "Dynamic Import Protocol" and "Auto-Initializing Workers" to significantly improve the Developer Experience (DX) for worker-based components (like Sparkline, Canvas).

Goal: Enable developers to drop in advanced, worker-backed components without requiring manual configuration (useCanvasWorker: true) or boilerplate code (canvas.mjs).

Strategy:

On-Demand Worker Start: The Main Thread (Neo.worker.Manager) will expose a method to start workers (e.g., 'canvas') dynamically if they are not already running.
Dynamic Module Loading: The Neo.worker.Base class will expose a loadModule method, allowing any worker to import scripts (renderers) at runtime.
Smart Component Logic: Components will orchestrate this process: "Start Worker" -> "Load Renderer" -> "Register".

Roadmap:

Feat: Manager.startWorker: Implement the main thread logic to spawn workers on demand.
Refactor: worker.Base.loadModule: Centralize module loading logic in the base worker class.
Feat: Smart Initialization: Update SparklineComponent (as a PoC) to auto-initialize its environment.
Feat: Generic Sparkline Column: Create a Neo.grid.column.Sparkline that wraps this logic for easy grid integration.

tobiu added the epic label on Feb 2, 2026, 2:59 PM

tobiu added the developer-experience label on Feb 2, 2026, 2:59 PM

tobiu added the ai label on Feb 2, 2026, 2:59 PM

tobiu added the architecture label on Feb 2, 2026, 2:59 PM

tobiu added sub-issue #8949 on Feb 2, 2026, 3:00 PM

tobiu added sub-issue #8950 on Feb 2, 2026, 3:00 PM

tobiu added sub-issue #8951 on Feb 2, 2026, 3:01 PM

tobiu assigned to @tobiu on Feb 2, 2026, 3:29 PM

tobiu added sub-issue #8952 on Feb 2, 2026, 10:31 PM

tobiu cross-referenced by #8952 on Feb 2, 2026, 10:39 PM

tobiu added sub-issue #8953 on Feb 2, 2026, 10:50 PM

tobiu added sub-issue #8954 on Feb 2, 2026, 11:39 PM

tobiu added sub-issue #8955 on Feb 2, 2026, 11:54 PM

tobiu Feb 2, 2026, 11:54 PM

Input from Gemini 3 Pro:

✦ I have successfully completed the Dynamic Worker Architecture & Import Protocol epic.

Achievements:

Dynamic Worker Orchestration: Implemented Neo.worker.Manager.startWorker (#8949) to allow on-demand spawning of workers (e.g., 'canvas') from the main thread.

Protocol Standardization: Centralized module loading in Neo.worker.Base (#8950), enabling any worker to dynamically import scripts.

Zero-Config Components: Created Neo.component.Sparkline (#8954) and Neo.canvas.Sparkline (#8955) as a fully autonomous pair. The component orchestrates the worker start, module load, and renderer registration automatically.

Grid Integration: Delivered Neo.grid.column.Sparkline for seamless usage in data grids.

Robustness: Solved race conditions (#8952) and made the canvas worker entry point optional (#8953), ensuring existing apps remain stable while new features are "opt-in".

Outcome: Developers can now simply use {type: 'sparkline', dataField: '...'} in a grid column, and the framework handles the entire multi-threaded complexity (starting the worker, loading the renderer, syncing state) transparently. This significantly improves the Developer Experience (DX) for advanced visualizations.

tobiu closed this issue on Feb 2, 2026, 11:54 PM

tobiu cross-referenced by #8930 on Feb 3, 2026, 12:03 AM