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	8830
title	Stabilize VDOM Unit Tests: Eliminate ID Collisions in Parallel Execution
state	Closed
labels	airefactoringtesting
assignees	tobiu
createdAt	Jan 20, 2026, 5:12 PM
updatedAt	Jan 20, 2026, 5:18 PM
githubUrl	https://github.com/neomjs/neo/issues/8830
author	tobiu
commentsCount	1
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Jan 20, 2026, 5:18 PM

Stabilize VDOM Unit Tests: Eliminate ID Collisions in Parallel Execution

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

Closed v11.23.0 airefactoringtesting

tobiu commented on Jan 20, 2026, 5:12 PM

This ticket addresses the instability of the VDOM unit test suite when running with multiple workers (parallel execution).

The Problem: Running npm run test-unit resulted in sporadic failures and numerous [Base.mjs] Trying to create an item with an already existing id errors. This was caused by several test files (specifically RaceCondition.spec.mjs and TreeBuilder.spec.mjs) using hardcoded component IDs (e.g., 'child-1', 'test-container'). When Playwright executed these tests in parallel or reused workers without perfect cleanup, these IDs collided, leading to cross-test pollution and failures.

The Solution: Refactor the affected test files to use dynamic, unique IDs for all components created during testing.

Introduced a helper function to generate unique IDs (e.g., ${prefix}-${timestamp}-${counter}).
Updated RaceCondition.spec.mjs and TreeBuilder.spec.mjs to use these dynamic IDs.
Ensured proper cleanup of dynamically created components in test.afterEach.

Outcome: The full unit test suite now passes consistently with 8 workers, with no ID collision errors.

tobiu added the ai label on Jan 20, 2026, 5:12 PM

tobiu added the refactoring label on Jan 20, 2026, 5:12 PM

tobiu added the testing label on Jan 20, 2026, 5:12 PM

tobiu referenced in commit 5c3ca3b - "test: Stabilize VDOM Unit Tests: Eliminate ID Collisions in Parallel Execution (#8830)" on Jan 20, 2026, 5:17 PM

tobiu assigned to @tobiu on Jan 20, 2026, 5:17 PM

tobiu Jan 20, 2026, 5:17 PM

Input from Gemini 3 Pro:

✦ I have refactored RaceCondition.spec.mjs and TreeBuilder.spec.mjs to use dynamic, unique IDs for all test components.

Changes:

Implemented a getUniqueId helper in test files.

Replaced hardcoded IDs (e.g., 'child-1') with generated ones (e.g., 'child-1-1705...').

Updated teardown logic to track and destroy these dynamically named components.

Verification: npm run test-unit now passes 240/240 tests consistently with 8 workers, and the ID collision errors are gone.

tobiu closed this issue on Jan 20, 2026, 5:18 PM