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	9019
title	Fix Playwright Teleportation Tests for Fixed-DOM-Order Grid
state	Closed
labels	aitestingregression
assignees	tobiu
createdAt	Feb 6, 2026, 7:14 PM
updatedAt	Feb 6, 2026, 7:51 PM
githubUrl	https://github.com/neomjs/neo/issues/9019
author	tobiu
commentsCount	1
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Feb 6, 2026, 7:51 PM

Fix Playwright Teleportation Tests for Fixed-DOM-Order Grid

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

Closed v12.0.0 aitestingregression

tobiu commented on Feb 6, 2026, 7:14 PM

Objective: Update test/playwright/unit/grid/Teleportation.spec.mjs to align with the new "Fixed-DOM-Order" Row Pooling architecture. The current tests fail because they expect behaviors (DOM moves, direct VDOM structure access) that have been intentionally obsoleted by recent refactorings (#9012, #9017).

Issue 1: Expectation Mismatch (Zero Moves)

Failure: expect(moveNodes.length).toBe(3) received 0.
Reason: The Fixed-DOM-Order strategy eliminates moveNode operations for rows during scrolling.
Fix: Update the test to expect 0 move deltas for rows. Verify text updates count and adjust if necessary.

Issue 2: VDOM Traversal Failure

Failure: TypeError: Cannot read properties of undefined (reading '1') when accessing firstRenderedRow.cn[1].
Reason: GridBody now contains Neo.grid.Row references (placeholders) in its vdom.cn, not the full VDOM tree of the rows. The test tries to access cell cn[1] directly from the Body's VDOM, which is no longer valid.
Fix:
- Resolve the Neo.grid.Row instance from the Body's items (using getComponent).
- Access the Row's own vdom property to inspect cells and content.

Plan:

Modify Teleportation.spec.mjs to assert moveNodes.length is 0.
Refactor the DOM inspection logic to retrieve the Row component instance before inspecting its VDOM structure.
Run the test to verify stability.

Related:

#9017 (Grid Body Refactor)
#9012 (Fixed-DOM-Order)

tobiu added the ai label on Feb 6, 2026, 7:14 PM

tobiu added the testing label on Feb 6, 2026, 7:14 PM

tobiu added the regression label on Feb 6, 2026, 7:14 PM

tobiu referenced in commit 0524911 - "test: Fix Teleportation specs for Fixed-DOM-Order Grid (#9019)" on Feb 6, 2026, 7:51 PM

tobiu Feb 6, 2026, 7:51 PM

Input from Gemini 3 Pro:

✦ I have updated test/playwright/unit/grid/Teleportation.spec.mjs to align with the new Fixed-DOM-Order architecture.

Changes:

Updated Expectations:

moveNodes expectation set to 0 (was 3 or 8), confirming that rows are recycled in-place without moving in the DOM.

insertNodes expectation set to 0 (was 3), confirming full pool reuse.

textUpdates expectation set to 14 (was 11), accounting for the recycling of previously "inserted" rows.

Robust Row Inspection:

Refactored the test logic to identify rows by checking the component's rowIndex property, rather than assuming cn[0] corresponds to the top logical row. This handles the visual wrapping inherent in the fixed-order strategy.

Async Synchronization:

Added await grid.timeout(50) after scrolling to allow child component updates (e.g., Button text) to fully settle before assertions, resolving race conditions in the test environment.

VDOM Inspection:

Updated assertions to check .text instead of .html on button text nodes, matching Neo.button.Base implementation.

All tests are now passing. Code pushed to dev.

tobiu assigned to @tobiu on Feb 6, 2026, 7:51 PM

tobiu closed this issue on Feb 6, 2026, 7:51 PM