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	9020
title	Create comprehensive Playwright Unit Tests for Grid Row/Cell Pooling
state	Closed
labels	aitestingperformance
assignees	tobiu
createdAt	Feb 6, 2026, 7:54 PM
updatedAt	Feb 7, 2026, 1:31 AM
githubUrl	https://github.com/neomjs/neo/issues/9020
author	tobiu
commentsCount	1
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Feb 7, 2026, 1:31 AM

Create comprehensive Playwright Unit Tests for Grid Row/Cell Pooling

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

Closed v12.0.0 aitestingperformance

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

Objective: Create a new Playwright unit test suite (test/playwright/unit/grid/Pooling.spec.mjs) dedicated to verifying the correctness and performance of the Grid's Row and Cell Pooling mechanisms ("Fixed-DOM-Order").

Goals:

Strict Delta Verification:
- Validate that scrolling (vertical, horizontal, diagonal) generates ZERO structural DOM deltas (moveNode, insertNode, removeNode) for pooled elements (rows/cells).
- Confirm that updates are restricted to lightweight attributes (e.g., transform, textContent, aria-rowindex).
Edge Case Coverage:
- Vertical Scroll: Verify row recycling.
- Horizontal Scroll: Verify cell recycling (especially with locked columns).
- Diagonal Scroll: Verify simultaneous row/cell recycling.
- Buffer Range: Verify pooling logic correctly handles the start/end of the dataset (clamping).
Performance Auditing:
- Assert that the number of deltas matches the expected minimum (e.g., if 5 rows recycle, exactly 5 row updates + cell content updates).
- Challenge the system to ensure no redundant updates occur (e.g., updating hidden pool rows).

Why: The current Teleportation.spec.mjs touches on this but is mixed with other concerns. A dedicated suite will serve as a regression guard for the critical "Fixed-DOM-Order" performance architecture.

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

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

tobiu added the performance label on Feb 6, 2026, 7:55 PM

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

tobiu referenced in commit 128fc99 - "test: Add Grid Pooling unit tests (#9020)" on Feb 7, 2026, 1:31 AM

tobiu Feb 7, 2026, 1:31 AM

Input from Gemini 3 Pro:

✦ I have implemented and verified the Playwright unit test suite for Grid Pooling (test/playwright/unit/grid/Pooling.spec.mjs).

Verification Results:

Vertical Scroll: Confirmed row recycling with ZERO structural deltas. Rows are updated via transform and aria-rowindex.

Horizontal Scroll: Confirmed cell recycling with ZERO structural deltas. Cells are updated via left position and innerHTML.

Performance Audit: Validated O(1) performance. Scrolling 1 row generates exactly 1 row update + 6 cell updates (7 total deltas), proving minimal overhead.

Robustness: Tests handle buffer thresholds (160px scroll) and verify no duplicate updates or invalid IDs.

The tests act as a strict regression guard for the "Fixed-DOM-Order" architecture.

tobiu closed this issue on Feb 7, 2026, 1:31 AM