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	8599
title	Optimize updateVtext to be non-destructive and O(1)
state	Closed
labels	enhancementaiperformance
assignees	tobiu
createdAt	Jan 13, 2026, 3:14 PM
updatedAt	Jan 13, 2026, 3:16 PM
githubUrl	https://github.com/neomjs/neo/issues/8599
author	tobiu
commentsCount	1
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Jan 13, 2026, 3:16 PM

Optimize updateVtext to be non-destructive and O(1)

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

Closed v11.21.0 enhancementaiperformance

tobiu commented on Jan 13, 2026, 3:14 PM

Currently, Neo.main.DeltaUpdates.updateVtext updates virtual text nodes by rewriting the innerHTML of the parent element using a regex. This is:

Destructive: It destroys the state (focus, input values, scroll) of all sibling nodes in the same parent.
Slow: It forces a re-parse of the entire parent content (O(N)).

The goal is to re-implement updateVtext to:

Locate the start comment node () using DomAccess.
Update the nodeValue of the specific text node sibling directly.
Avoid touching innerHTML entirely.

tobiu added the enhancement label on Jan 13, 2026, 3:14 PM

tobiu added the ai label on Jan 13, 2026, 3:14 PM

tobiu added the performance label on Jan 13, 2026, 3:14 PM

tobiu assigned to @tobiu on Jan 13, 2026, 3:15 PM

tobiu referenced in commit 3cf0c95 - "perf: Optimize updateVtext to use direct DOM manipulation (#8599) on Jan 13, 2026, 3:16 PM

tobiu Jan 13, 2026, 3:16 PM

Input from Gemini 3 Pro:

✦ I have replaced the destructive innerHTML based implementation of updateVtext with a precise, non-destructive DOM manipulation approach.

Changes:

Logic: Instead of parsing a regex over the entire parent's HTML, the code now searches the parent's childNodes for the specific comment node containing the VNode ID ().

Update: Once found, it directly updates the nodeValue of the immediate nextSibling (which is the Text Node).

Impact:

Performance: Changed from O(N) (string parsing) to O(N) (DOM traversal) but with significantly lower constant factor and zero browser re-layout cost for siblings.

State: Sibling nodes no longer lose focus, selection, or input values because the parent's innerHTML is never touched.

Changes pushed to dev.

tobiu closed this issue on Jan 13, 2026, 3:16 PM