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	8900
title	Implement JIT ID Generation in TreeBuilder
state	Closed
labels	enhancementaicore
assignees	tobiu
createdAt	Jan 28, 2026, 4:29 PM
updatedAt	Jan 28, 2026, 5:41 PM
githubUrl	https://github.com/neomjs/neo/issues/8900
author	tobiu
commentsCount	1
parentIssue	8899
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Jan 28, 2026, 5:41 PM

Implement JIT ID Generation in TreeBuilder

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

Closed v11.24.0 enhancementaicore

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

Objective: Implement the "App Authority" logic for VDOM IDs by modifying TreeBuilder to generate IDs just-in-time (JIT) during payload construction.

Tasks:

Modify src/util/vdom/TreeBuilder.mjs:
- Update #buildTree method.
- When processing a node in VDOM mode (where childKey is effectively for VDOM construction), check if node.id is missing.
- If missing, generate a new ID using Neo.getId('neo-vnode').
- Crucial: Assign this ID in-place to the node object (mutation) to ensure the ID persists on the VDOM blueprint for future updates.
- Ensure this logic runs before any child recursion.
Modify src/vdom/VNode.mjs:
- Remove the current ID auto-generation logic (Neo.getId(...)).
- Change the constructor to throw an error if config.id is missing.
- This enforces the contract that all nodes arriving at the VDOM Worker must already have IDs.

Constraint:

Respect the existing ID prefix conventions (vnode vs vtext).
Ensure removeDom: true nodes also get IDs (to preserve identity if they are re-shown).

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

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

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

tobiu cross-referenced by #8901 on Jan 28, 2026, 4:29 PM

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

tobiu referenced in commit a1a369b - "feat: Implement JIT ID Generation in TreeBuilder (Ticket #8900)" on Jan 28, 2026, 4:48 PM

tobiu Jan 28, 2026, 4:49 PM

Input from Gemini 3 Pro:

✦ I have implemented the JIT ID generation logic.

Changes:

Modified src/util/vdom/TreeBuilder.mjs:

Added JIT ID generation in #buildTree when running in VDOM mode (childKey === 'cn').

Uses Neo.getId('vtext') for text nodes and Neo.getId('vnode') for others.

Assigns IDs in-place to the source VDOM node to ensure persistence.

Modified src/vdom/VNode.mjs:

Removed auto-generation fallback.

Now throws an error if config.id is missing, enforcing the App-Worker authority.

Next Steps: I will proceed with Ticket #8901 (Cleanup) in this same branch.

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

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