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	8469
title	Audit and Refactor all afterSetId Implementations
state	Closed
labels	epicairefactoringcore
assignees	tobiu
createdAt	Jan 9, 2026, 4:17 PM
updatedAt	Jan 9, 2026, 6:26 PM
githubUrl	https://github.com/neomjs/neo/issues/8469
author	tobiu
commentsCount	2
parentIssue	null
subIssues	8471 Refactor afterSetId in src/button/Base.mjs 8472 Implement Lazy VDOM Cloning in Component Base 8473 Refactor afterSetId in Split Button and Grid Body 8474 Enforce Eager VDOM Cloning in Component Constructor 8475 Remove redundant ensureStableIds from Button Base 8476 Refactor Gallery to remove manual afterSetId ID assignment 8477 Refactor Progress Component ID handling 8478 Refactor afterSetId in Form Fields to ensureStableIds
subIssuesCompleted	8
subIssuesTotal	8
blockedBy	[]
blocking	[]
closedAt	Jan 9, 2026, 6:26 PM

Audit and Refactor all afterSetId Implementations

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

Closed v11.19.1 epicairefactoringcore

tobiu commented on Jan 9, 2026, 4:17 PM

Following the VDOM ID stabilization fix (#8467), we need to audit all occurrences of afterSetId in the codebase.

Context: We discovered that Component.Base#afterSetId was previously mutating the class prototype's _vdom and that manual VDOM ID assignment is now handled centrally by VdomLifecycle#ensureStableIds.

Goals:

Redundancy Removal: Identify and remove any manual VDOM ID assignment logic that is now handled by ensureStableIds.
Safety Check: Ensure no other implementations are mutating class prototypes (e.g., modifying _vdom or vdom properties during the construction phase before initConfig completes).
Compatibility: Verify that component-specific logic (e.g., updating ARIA attributes, specific DOM lookups) is compatible with the new wrapper ID scheme.

Files to Audit:

src/button/Base.mjs
src/button/Split.mjs
src/component/Abstract.mjs
src/component/Base.mjs (Already refactored, double-check)
src/component/Gallery.mjs
src/component/Progress.mjs
src/core/Base.mjs
src/grid/Body.mjs

tobiu added the epic label on Jan 9, 2026, 4:17 PM

tobiu added the ai label on Jan 9, 2026, 4:17 PM

tobiu added the refactoring label on Jan 9, 2026, 4:17 PM

tobiu added the core label on Jan 9, 2026, 4:17 PM

tobiu assigned to @tobiu on Jan 9, 2026, 5:08 PM

tobiu added sub-issue #8471 on Jan 9, 2026, 5:09 PM

tobiu Jan 9, 2026, 5:09 PM

Input from Gemini 3 Pro:

✦ Completed refactoring of src/button/Base.mjs in sub-ticket #8471.

Replaced afterSetId with ensureStableIds.

Verified prototype safety with new unit tests.

tobiu added sub-issue #8472 on Jan 9, 2026, 5:26 PM

tobiu added sub-issue #8473 on Jan 9, 2026, 5:34 PM

tobiu added sub-issue #8474 on Jan 9, 2026, 5:43 PM

tobiu added sub-issue #8475 on Jan 9, 2026, 5:57 PM

tobiu added sub-issue #8476 on Jan 9, 2026, 6:07 PM

tobiu added sub-issue #8477 on Jan 9, 2026, 6:14 PM

tobiu added sub-issue #8478 on Jan 9, 2026, 6:21 PM

tobiu Jan 9, 2026, 6:26 PM

Input from Gemini 3 Pro:

✦ I have completed the audit and refactoring of all afterSetId implementations.

Summary of Work:

Core Safety: Implemented eager VDOM cloning in Neo.component.Base.construct (#8474) to prevent prototype pollution from early VDOM access.

Logic Centralization:

Refactored src/button/Split.mjs, src/grid/Body.mjs, src/component/Progress.mjs, src/component/Gallery.mjs, src/form/field/CheckBox.mjs, src/form/field/FileUpload.mjs, and src/form/field/Text.mjs.

Replaced manual afterSetId logic with ensureStableIds overrides where appropriate.

Removed redundant ensureStableIds from src/button/Base.mjs.

Audit: Verified that src/component/Abstract.mjs and src/core/Base.mjs use afterSetId correctly for manager registration, which is outside the scope of VDOM stabilization.

Outcome: The codebase now enforces a consistent, safe, and centralized pattern for VDOM ID assignment.

I am closing this Epic.

tobiu closed this issue on Jan 9, 2026, 6:26 PM