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	8836
title	Architecture: Optimize `vdom.Helper.updateBatch` Response Payload
state	Closed
labels	aiarchitectureperformancecore
assignees	tobiu
createdAt	Jan 20, 2026, 10:00 PM
updatedAt	Jan 20, 2026, 11:06 PM
githubUrl	https://github.com/neomjs/neo/issues/8836
author	tobiu
commentsCount	1
parentIssue	8834
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Jan 20, 2026, 11:06 PM

Architecture: Optimize `vdom.Helper.updateBatch` Response Payload

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

Closed v11.23.0 aiarchitectureperformancecore

tobiu commented on Jan 20, 2026, 10:00 PM

Currently, vdom.Helper.updateBatch returns both deltas (DOM operations) and vnodes (new VNode state) in the same response message. Since this message is forwarded from Vdom Worker -> Main -> App, the large vnodes payload traverses the Main thread unnecessarily, and the deltas payload traverses to the App thread unnecessarily.

Goal: Split the response flow to avoid doubling the payload size.

Proposed Strategy:

Vdom -> Main: Send deltas only. Main consumes them.
Vdom -> App: Send vnodes (results) directly? Or have Main strip deltas before forwarding?
Alternatively, implement VDomUtil.applyDeltas(vnode, deltas) on the App side to reconstruct state from deltas, eliminating the need to send vnodes entirely.

Tasks:

Investigate feasibility of applyDeltas for VNode state.
Implement payload splitting or reconstruction.

tobiu added the ai label on Jan 20, 2026, 10:00 PM

tobiu added the architecture label on Jan 20, 2026, 10:00 PM

tobiu added the performance label on Jan 20, 2026, 10:00 PM

tobiu added the core label on Jan 20, 2026, 10:00 PM

tobiu added parent issue #8834 on Jan 20, 2026, 10:00 PM

tobiu referenced in commit 8525ee0 - "refactor: Update vdom.Helper.updateBatch to return vnodes Map (#8836) on Jan 20, 2026, 10:01 PM

tobiu assigned to @tobiu on Jan 20, 2026, 10:01 PM

tobiu Jan 20, 2026, 10:01 PM

Input from Gemini 3 Pro:

✦ Completed refactoring of updateBatch return signature.

Now returns { vnodes: { [id]: vnode } } instead of an array.

Updated executeVdomUpdate to consume the map.

This prepares for further payload optimizations (e.g. splitting deltas/results).

Verified tests pass.

Pushed to epic-8834.

tobiu cross-referenced by #8837 on Jan 20, 2026, 10:13 PM

tobiu closed this issue on Jan 20, 2026, 11:06 PM

Architecture: Optimize vdom.Helper.updateBatch Response Payload

Architecture: Optimize `vdom.Helper.updateBatch` Response Payload