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	9074
title	Epic: Framework-wide Adoption of ''internalId'' for Stable DOM Identity
state	Closed
labels	epicairefactoringcore
assignees	tobiu
createdAt	Feb 9, 2026, 11:51 AM
updatedAt	Feb 10, 2026, 1:58 AM
githubUrl	https://github.com/neomjs/neo/issues/9074
author	tobiu
commentsCount	1
parentIssue	null
subIssues	9071 refactor: Adopt ''internalId'' for Stable DOM Keying (List & Data Views) 9072 refactor: Adopt ''internalId'' for Stable DOM Keying (Grid & Table) 9073 refactor: Ensure Drag & Drop Stability via ''internalId''
subIssuesCompleted	3
subIssuesTotal	3
blockedBy	[]
blocking	[]
closedAt	Feb 10, 2026, 1:58 AM

Epic: Framework-wide Adoption of 'internalId' for Stable DOM Identity

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

Closed v12.0.0 epicairefactoringcore

tobiu commented on Feb 9, 2026, 11:51 AM

This Epic tracks the systematic refactoring of framework components to utilize the newly implemented internalId (#9070) for DOM keying.

Context: The internalId feature (#9070) provides a stable, globally unique neo-record-x identity for all store items (Records and Raw Objects). Adopting this across the framework will:

Eliminate "Phantom Record" Issues: Correctly render new records (id: null) without DOM collisions.
Ensure DOM Stability: Prevent full re-renders when a record's DB ID changes (e.g. on save).
Enhance Security: Decouple DOM IDs from Database IDs.
Fix Drag & Drop: Prevent ID collisions when dragging items between stores.

Implementation Plan: Systematic rollout across three key areas:

List & Data Views: Base classes for lists, galleries, and helix views.
Grid & Table: Container, View, and Row architectures.
Drag & Drop: DragZones and DropZones for cross-store operations.

Child Issues:

#9071 (List & Data Views)
#9072 (Grid & Table)
#9073 (Drag & Drop)

tobiu added the epic label on Feb 9, 2026, 11:51 AM

tobiu added the ai label on Feb 9, 2026, 11:51 AM

tobiu added the refactoring label on Feb 9, 2026, 11:51 AM

tobiu added the core label on Feb 9, 2026, 11:51 AM

tobiu added sub-issue #9071 on Feb 9, 2026, 11:52 AM

tobiu added sub-issue #9072 on Feb 9, 2026, 11:52 AM

tobiu added sub-issue #9073 on Feb 9, 2026, 11:52 AM

tobiu assigned to @tobiu on Feb 9, 2026, 1:33 PM

tobiu Feb 10, 2026, 1:58 AM

resolved.

tobiu closed this issue on Feb 10, 2026, 1:58 AM