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	8596
title	Enhance VDOM ID Stability to Remove Manual ID Requirement in TreeList
state	Closed
labels	bugaicore
assignees	tobiu
createdAt	Jan 13, 2026, 2:11 PM
updatedAt	Jan 13, 2026, 2:38 PM
githubUrl	https://github.com/neomjs/neo/issues/8596
author	tobiu
commentsCount	1
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Jan 13, 2026, 2:38 PM

Enhance VDOM ID Stability to Remove Manual ID Requirement in TreeList

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

Closed v11.21.0 bugaicore

tobiu commented on Jan 13, 2026, 2:11 PM

Context: The recent fix for the TreeList "Chimera Bug" (#8595) involved manually assigning deterministic IDs to UL containers to prevent Neo.util.VDom.syncVdomState from erroneously assigning them IDs from sibling LI nodes during race conditions.

Problem: While effective, this manual ID assignment feels like a workaround ("monkey patching"). The framework's core VDOM engine, specifically Neo.util.VDom.syncVdomState and Neo.vdom.Helper, should theoretically be robust enough to handle dynamic nodes without requiring manual IDs for every structural element. The goal of ensureStableIds and similar initiatives was to make this automatic.

Objective:

Investigate why syncVdomState fails to distinguish between the UL container and the LI item when the UL appears dynamically.
Create a focused reproduction case (unit test) that isolates syncVdomState behavior with dynamic sibling nodes where one lacks an ID.
Implement a fix in src/util/VDom.mjs or src/vdom/Helper.mjs that makes the manual UL ID assignment in TreeList unnecessary.
Verify the fix by removing the manual ID from TreeList and running the race condition tests.

Goal: Ensure Neo.tree.List (and other components) works robustly with purely dynamic IDs for container elements.

tobiu added the bug label on Jan 13, 2026, 2:11 PM

tobiu added the ai label on Jan 13, 2026, 2:11 PM

tobiu added the core label on Jan 13, 2026, 2:11 PM

tobiu assigned to @tobiu on Jan 13, 2026, 2:11 PM

tobiu referenced in commit ff6dd1f - "fix(vdom): Prevent Chimera VDOM corruption in syncVdomState (#8596) on Jan 13, 2026, 2:35 PM

tobiu Jan 13, 2026, 2:36 PM

Input from Gemini 3 Pro:

✦ I have implemented a core VDOM fix for the Chimera Bug and reverted the manual workaround in TreeList.

Changes:

Core VDOM Fix (src/util/VDom.mjs): Modified syncVdomState to abort ID synchronization if the node tags (vnode.nodeName vs vdom.tag) do not match. This prevents the "Chimera" scenario where a UL container (appearing dynamically) inherits the ID of a sibling LI item during a race condition.

TreeList Revert (src/tree/List.mjs): Removed the manual ID assignment (parentId + '__ul') introduced in the previous fix. The core VDOM engine now handles this safely.

New Unit Test (test/playwright/unit/vdom/SyncVdomState.spec.mjs): Added a dedicated test suite for syncVdomState that explicitly reproduces the mismatched-tag scenario and asserts that IDs are NOT synced.

Test Fix (test/playwright/unit/draggable/container/SortZone.spec.mjs): Fixed a flaky test failure by explicitly importing VdomHelper, which was previously relying on implicit global state from other tests.

Verification:

npx playwright test test/playwright/unit/vdom/SyncVdomState.spec.mjs ✅ Passed

npx playwright test test/playwright/unit/tree/ListRaceCondition.spec.mjs ✅ Passed (without manual IDs)

All unit tests passed locally.

The changes have been pushed to dev.

tobiu cross-referenced by #8592 on Jan 13, 2026, 2:37 PM

tobiu closed this issue on Jan 13, 2026, 2:38 PM