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	9210
title	Regression: Unit Test Failures in Teleportation.spec.mjs after #9200
state	Closed
labels	bugaitestingregression
assignees	tobiu
createdAt	Feb 19, 2026, 1:52 PM
updatedAt	Feb 19, 2026, 2:12 PM
githubUrl	https://github.com/neomjs/neo/issues/9210
author	tobiu
commentsCount	2
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Feb 19, 2026, 2:12 PM

Regression: Unit Test Failures in Teleportation.spec.mjs after #9200

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

Closed v12.0.0 bugaitestingregression

tobiu commented on Feb 19, 2026, 1:52 PM

Unit tests in test/playwright/unit/grid/Teleportation.spec.mjs are failing with TypeError: Cannot read properties of undefined (reading '0') when accessing cell.cn[0].

This started happening after the introduction of Neo.grid.column.Component optimization (Issue #9200).

Hypothesis: The optimization relies on record.version to short-circuit updates. If Teleportation.spec.mjs uses plain objects (where version is undefined), the optimization might trigger incorrectly (undefined === undefined), preventing components from rendering or updating when they should.

Objective:

Investigate Teleportation.spec.mjs to understand how it mocks data.
Fix Neo.grid.column.Component to handle cases where record.version is undefined (fallback to standard update).
Ensure unit tests pass.

tobiu added the bug label on Feb 19, 2026, 1:52 PM

tobiu added the ai label on Feb 19, 2026, 1:52 PM

tobiu added the testing label on Feb 19, 2026, 1:52 PM

tobiu added the regression label on Feb 19, 2026, 1:52 PM

tobiu Feb 19, 2026, 2:11 PM

Input from Gemini 3 Pro:

✦ Resolved regression in test/playwright/unit/grid/Teleportation.spec.mjs.

Root Cause: The test failure was unrelated to the new Record Versioning feature. It was a pre-existing fragility in the test code that was exposed by the environment change (possibly test sharding or load).

The test assumed that rowComponent.vdom.cn[1] always corresponded to the second logical column. However, Neo.grid.column.Component uses hideMode: 'visibility', which classifies it as a "Permanent Cell" in Neo.grid.Row's architecture. Permanent cells are appended after the fixed "Pooled Cells" array.

In the test scenario:

Column 0 (ID): Pooled (Index 0)

Column 1 (Component): Permanent (Appended at Index 20, assuming pool size 20)

cn[1] was actually a hidden placeholder cell from the pool, which naturally had no content, causing cell.cn[0] to throw "Cannot read properties of undefined".

Fix: Updated Teleportation.spec.mjs to robustly locate the component cell by inspecting the VDOM content (vdom.cn.find(...)) rather than relying on a hardcoded index. I also added detailed JSDoc to the test file to explain this "Full Pool Rendering" structure for future reference.

tobiu Feb 19, 2026, 2:12 PM

resolved via https://github.com/neomjs/neo/commit/fe0169af31c9740e5d798d8473783f9b2b1b3867

tobiu closed this issue on Feb 19, 2026, 2:12 PM

tobiu assigned to @tobiu on Feb 19, 2026, 2:12 PM