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	8307
title	Neural Link: Support depth in getVdomTree and getVnodeTree
state	Closed
labels	enhancementai
assignees	tobiu
createdAt	Jan 4, 2026, 12:15 PM
updatedAt	Jan 4, 2026, 12:40 PM
githubUrl	https://github.com/neomjs/neo/issues/8307
author	tobiu
commentsCount	1
parentIssue	8169
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Jan 4, 2026, 12:40 PM

Neural Link: Support depth in getVdomTree and getVnodeTree

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

Closed v11.18.0 enhancementai

tobiu commented on Jan 4, 2026, 12:15 PM

We need to update getVdomTree and getVnodeTree in src/ai/client/ComponentService.mjs to support a configured depth.

Currently, these methods return the raw vdom or vnode property of the component, which does not expand child component references or respect a depth limit.

We will leverage src/util/vdom/TreeBuilder.mjs to generate the trees with the specified depth.

Requirements:

Update getVdomTree to accept depth and use TreeBuilder.getVdomTree.
Update getVnodeTree to accept depth and use TreeBuilder.getVnodeTree.
Default depth should be -1 (infinite) if not specified, matching TreeBuilder defaults.

Context: Real-world usage in src/mixin/VdomLifecycle.mjs demonstrates using TreeBuilder for scoped updates.

tobiu added the enhancement label on Jan 4, 2026, 12:15 PM

tobiu added the ai label on Jan 4, 2026, 12:15 PM

tobiu assigned to @tobiu on Jan 4, 2026, 12:16 PM

tobiu added parent issue #8169 on Jan 4, 2026, 12:16 PM

tobiu referenced in commit 77d016e - "Neural Link: Support depth in getVdomTree and getVnodeTree #8307" on Jan 4, 2026, 12:39 PM

tobiu Jan 4, 2026, 12:39 PM

Input from Gemini 2.5 pro:

✦ I have verified the server-side implementation and the API definition:

ai/mcp/server/neural-link/openapi.yaml: The get_vdom_tree and get_vnode_tree operations use GetComponentTreeRequest schema, which correctly defines the depth parameter (integer).

ai/mcp/server/neural-link/services/ComponentService.mjs: The getVdomTree and getVnodeTree methods correctly forward the depth parameter to the ConnectionService.

ai/mcp/server/neural-link/services/toolService.mjs: Correctly binds the methods.

The missing link was purely in the client-side src/ai/client/ComponentService.mjs, which ignored the passed depth. This has been rectified.

The full stack now supports depth for VDOM/VNode inspection.

tobiu closed this issue on Jan 4, 2026, 12:40 PM