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	8849
title	Fix VDOM Teleportation Regression: Restore Window Context in updateBatch
state	Closed
labels	bugairegressioncore
assignees	tobiu
createdAt	Jan 21, 2026, 1:27 PM
updatedAt	Jan 21, 2026, 1:39 PM
githubUrl	https://github.com/neomjs/neo/issues/8849
author	tobiu
commentsCount	1
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Jan 21, 2026, 1:39 PM

Fix VDOM Teleportation Regression: Restore Window Context in updateBatch

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

Closed v11.23.0 bugairegressioncore

tobiu commented on Jan 21, 2026, 1:27 PM

The recent refactoring for Batched Disjoint VDOM Updates (Teleportation) in src/mixin/VdomLifecycle.mjs inadvertently removed the logic that attaches appName and windowId to the VDOM update payload.

This metadata is critical for Neo.worker.mixin.RemoteMethodAccess to correctly route messages in SharedWorker environments, particularly when multiple windows (Main Threads) are connected to the same App Worker.

Symptom: Operations that involve moving components between windows (e.g., LivePreview popping out to a new window) fail to update the VDOM/DOM in the target window because the VDOM worker cannot route the reply correctly or the message channel context is lost.

Cause: executeVdomUpdate constructs a batchData object but fails to check currentWorker.isSharedWorker and attach the window context before calling Neo.vdom.Helper.updateBatch.

Fix: Restore the SharedWorker check and context assignment in executeVdomUpdate.

tobiu added the bug label on Jan 21, 2026, 1:27 PM

tobiu added the ai label on Jan 21, 2026, 1:27 PM

tobiu added the regression label on Jan 21, 2026, 1:27 PM

tobiu added the core label on Jan 21, 2026, 1:27 PM

tobiu referenced in commit 1ccd84a - "fix(VdomLifecycle): Restore windowId context in updateBatch for SharedWorkers (#8849)" on Jan 21, 2026, 1:38 PM

tobiu assigned to @tobiu on Jan 21, 2026, 1:38 PM

tobiu Jan 21, 2026, 1:39 PM

Input from Gemini 3 Pro:

✦ ✦ Fixed regression in src/mixin/VdomLifecycle.mjs.

Changes:

Restored the currentWorker.isSharedWorker check in executeVdomUpdate.

Injected appName and windowId into the updateBatch payload when running in a SharedWorker.

Added a strong, intent-driven comment explaining why this block is critical for RemoteMethodAccess routing and multi-window operations.

This restores the ability for the VDOM worker to correctly route update replies to the originating window in a SharedWorker environment.

tobiu closed this issue on Jan 21, 2026, 1:39 PM