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	8876
title	test: Fix Namespace Collisions in Unit Tests exposed by setupClass Guardrail
state	Closed
labels	refactoringtestingcore
assignees	tobiu
createdAt	Jan 24, 2026, 3:25 PM
updatedAt	Jan 24, 2026, 4:26 PM
githubUrl	https://github.com/neomjs/neo/issues/8876
author	tobiu
commentsCount	1
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Jan 24, 2026, 3:47 PM

test: Fix Namespace Collisions in Unit Tests exposed by setupClass Guardrail

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

Closed v11.24.0 refactoringtestingcore

tobiu commented on Jan 24, 2026, 3:25 PM

Description: We recently hardened Neo.setupClass to throw an error when Neo.config.unitTestMode is true and a namespace collision occurs. This prevents test isolation issues where different tests unintentionally share or overwrite class definitions.

This change has exposed existing collisions in our test suite, where multiple test files define classes with generic names like Mock.Component or Test.Container.

Goals:

Enforce Unique ClassNames: Update all failing tests to use unique, file-specific class names (e.g., Test.Unit.Vdom.TreeBuilder.MockComponent).
Verify Stability: Ensure the entire Playwright unit test suite passes with the new guardrail in place.

Known Failures:

test/playwright/unit/state/ProviderNestedDataConfigs.spec.mjs (Mock.Component)
test/playwright/unit/vdom/TreeBuilder.spec.mjs (Test.MockComponent)
test/playwright/unit/vdom/VdomLifecycle.spec.mjs (Test.MockComponent)
test/playwright/unit/vdom/VdomMerging.spec.mjs (Test.Container)

Action Plan: Iterate through the failing tests and rename the test classes to be unique.

tobiu added the refactoring label on Jan 24, 2026, 3:25 PM

tobiu added the testing label on Jan 24, 2026, 3:25 PM

tobiu added the core label on Jan 24, 2026, 3:25 PM

tobiu referenced in commit 350770c - "test: Fix Namespace Collisions in Unit Tests exposed by setupClass Guardrail (#8876)" on Jan 24, 2026, 3:45 PM

tobiu assigned to @tobiu on Jan 24, 2026, 3:46 PM

tobiu Jan 24, 2026, 3:46 PM

Input from Gemini 3 Pro:

✦ I have resolved the namespace collisions in the unit test suite and enabled the new setupClass guardrail.

Implementation Details:

Hardened Neo.setupClass: Modified src/Neo.mjs to throw a specific error (Namespace collision in unitTestMode) when a namespace is redefined while Neo.config.unitTestMode is true. This ensures strict isolation for unit tests.

Fixed Test Suite Collisions: I identified and renamed colliding class definitions in the following test files to be unique and file-specific:

test/playwright/unit/state/ProviderNestedDataConfigs.spec.mjs: Mock.Component -> Test.Unit.State.ProviderNestedDataConfigs.MockComponent

test/playwright/unit/vdom/TreeBuilder.spec.mjs: Test.MockComponent -> Test.Unit.Vdom.TreeBuilder.MockComponent

test/playwright/unit/vdom/VdomLifecycle.spec.mjs: Test.MockComponent -> Test.Unit.Vdom.VdomLifecycle.MockComponent

test/playwright/unit/vdom/VdomMerging.spec.mjs: Test.Container -> Test.Unit.Vdom.VdomMerging.Container

test/playwright/unit/core/ClassConfigsAndFields.spec.mjs: Neo.TestClass -> Test.Unit.Core.ClassConfigsAndFields.TestClass and fixed Neo.core.Base collision.

test/playwright/unit/core/ClassSystem.spec.mjs: Neo.TestClass -> Test.Unit.Core.ClassSystem.TestClass

Note: The setupClass change is being committed NOW as part of this PR, effectively activating the guardrail for all future test runs.

The full unit test suite now passes with strict namespace enforcement enabled.

tobiu closed this issue on Jan 24, 2026, 3:47 PM