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	8901
title	Remove Obsolete ID Sync Logic from VDom.mjs
state	Closed
labels	airefactoringcore
assignees	tobiu
createdAt	Jan 28, 2026, 4:29 PM
updatedAt	Jan 28, 2026, 5:41 PM
githubUrl	https://github.com/neomjs/neo/issues/8901
author	tobiu
commentsCount	1
parentIssue	8899
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Jan 28, 2026, 5:41 PM

Remove Obsolete ID Sync Logic from VDom.mjs

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

Closed v11.24.0 airefactoringcore

tobiu commented on Jan 28, 2026, 4:29 PM

Objective: Clean up the codebase by removing the complex, brittle ID syncing logic that is rendered obsolete by the new App-Authority ID system (Ticket #8900).

Tasks:

Modify src/util/VDom.mjs:
- Refactor syncVdomState.
- Remove the ID syncing block (where it checks !vdom.id and assigns vnode.id).
- Remove the logic that checks for vnode.id !== vdom.id mismatches (these should now be impossible).
- Keep the scroll state synchronization (scrollTop, scrollLeft) and any other property syncing that is truly dynamic (e.g. value updates).
Modify src/mixin/VdomLifecycle.mjs:
- Refactor syncVnodeTree.
- Simplify the child component mapping logic. It no longer needs to rely on complex heuristics or index matching to find "stolen" nodes, as IDs are now guaranteed to match.
- Focus strictly on updating component vnode references and mounted state.

Constraint:

Ensure that rehydration (Functional Components getting scroll state from existing VNodes) still works.

tobiu added the ai label on Jan 28, 2026, 4:29 PM

tobiu added the refactoring label on Jan 28, 2026, 4:29 PM

tobiu added the core label on Jan 28, 2026, 4:29 PM

tobiu added parent issue #8899 on Jan 28, 2026, 4:34 PM

tobiu cross-referenced by #8900 on Jan 28, 2026, 4:49 PM

tobiu referenced in commit 565c307 - "refactor: Remove obsolete ID Sync logic from VDom.mjs (Ticket #8901)" on Jan 28, 2026, 4:50 PM

tobiu Jan 28, 2026, 4:50 PM

Input from Gemini 3 Pro:

✦ I have refactored src/util/VDom.mjs to remove the obsolete ID synchronization logic.

Changes:

Removed ID assignment block (VNode -> VDOM).

Removed ID mismatch guards.

Retained scroll state synchronization and recursive traversal for nested scroll containers.

Retained strict structure alignment (filtering removeDom: true) to ensure safe recursion.

Next Steps: I will proceed with Ticket #8902 (Verify Stability & Fix Tests). This is the critical phase where I expect some tests to fail due to the new strictness.

tobiu assigned to @tobiu on Jan 28, 2026, 5:41 PM

tobiu closed this issue on Jan 28, 2026, 5:41 PM