What is the Neural Link?

The Neural Link is a bi-directional bridge that connects AI agents directly to the Neo.mjs runtime. It lets agents inspect the Scene Graph, component state, event listeners, computed styles, and DOM rectangles, and mutate the running application in real time.

Why is Neo.mjs called an Application Engine instead of a framework?

Neo.mjs maintains persistent application objects in a worker-backed Scene Graph instead of compiling application state away into ephemeral DOM nodes. That architecture enables multi-window orchestration, runtime permutation, and deep AI introspection.

What is Context Engineering?

Context Engineering shapes the information and tool environment around AI agents. Neo.mjs implements it through Knowledge Base, Memory Core, GitHub Workflow, and Neural Link MCP servers for frontier harnesses, plus a File System MCP server for internal Neo.ai.Agent local loops.

What is the Neo.mjs Agent OS?

The Neo.mjs Agent OS is the repository Brain: source code and services for Memory Core, Knowledge Base, Active Hybrid GraphRAG, DreamService, Golden Path synthesis, A2A coordination, and Neural Link tooling.

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
contentTrust
projected
quarantined	0
signals	[]
blockedBy	[]
blocking	[]
closedAt	Jan 13, 2026, 3:16 PM

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

Closed v11.21.0/archive-v11-21-0-chunk-1 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 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.