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	8603
title	VDOM Helper Support for Fragment Indexing & Deltas
state	Closed
labels	aicorefeature
assignees	tobiu
createdAt	Jan 13, 2026, 3:52 PM
updatedAt	Jan 13, 2026, 4:52 PM
githubUrl	https://github.com/neomjs/neo/issues/8603
author	tobiu
commentsCount	1
parentIssue	8601
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Jan 13, 2026, 4:52 PM

VDOM Helper Support for Fragment Indexing & Deltas

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

Closed v11.21.0 aicorefeature

tobiu commented on Jan 13, 2026, 3:52 PM

Part of Epic #8601.

Goal: Update src/vdom/Helper.mjs to handle tag: 'fragment' correctly during index calculation and delta generation.

Architectural Decision: We are following a "Smart Runtime / Lean IPC" strategy. The VDOM Helper should NOT "compile away" fragments into individual node operations. Instead, it must generate high-level "Fragment Deltas" (e.g., {action: 'moveNode', id: fragmentId}) and rely on Neo.main.DeltaUpdates to handle the physical DOM range manipulation. This minimizes IPC traffic.

Tasks:

Update getPhysicalIndex:
- Logic must be generalized. Currently, it accounts for text nodes (1 logical = 3 physical).
- It must now account for Fragments (1 logical = N physical, where N is the recursive count of the Fragment's rendered children + anchors).
Update createDeltas:
- Ensure compareAttributes ignores attributes/styles for fragments (or warns).
- Ensure standard diffing logic generates insert/move/remove deltas for the Fragment node itself, not its constituents.

tobiu added the ai label on Jan 13, 2026, 3:52 PM

tobiu added the core label on Jan 13, 2026, 3:52 PM

tobiu added the feature label on Jan 13, 2026, 3:52 PM

tobiu added parent issue #8601 on Jan 13, 2026, 3:53 PM

tobiu cross-referenced by #8601 on Jan 13, 2026, 4:17 PM

tobiu assigned to @tobiu on Jan 13, 2026, 4:18 PM

tobiu referenced in commit 074a005 - "feat: VDOM Helper Support for Fragment Indexing & Deltas (#8603)" on Jan 13, 2026, 4:51 PM

tobiu Jan 13, 2026, 4:51 PM

Input from Gemini 3 Pro:

✦ I have updated src/vdom/Helper.mjs to support Fragments.

Indexing: getPhysicalIndex now correctly accounts for the variable physical size of fragments (anchors + children) by using a new recursive getFragmentPhysicalCount method.

Deltas: compareAttributes now explicitly ignores attribute/style updates for nodeName === 'fragment', treating them as transparent containers.

Ready for rendering engine updates.

tobiu closed this issue on Jan 13, 2026, 4:52 PM