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	9466
title	TreeGrid Big Data Demo: Create E2E Tests
state	Closed
labels	enhancementaitesting
assignees	tobiu
createdAt	Mar 13, 2026, 12:09 PM
updatedAt	Mar 13, 2026, 2:29 PM
githubUrl	https://github.com/neomjs/neo/issues/9466
author	tobiu
commentsCount	1
parentIssue	9461
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Mar 13, 2026, 2:29 PM

TreeGrid Big Data Demo: Create E2E Tests

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

Closed v12.1.0 enhancementaitesting

tobiu commented on Mar 13, 2026, 12:09 PM

Goal

Create comprehensive end-to-end (E2E) tests for the new TreeGrid Big Data demo using Playwright to ensure performance, stability, and correctness of core interactions (expand/collapse, scrolling, filtering) under heavy data loads.

Inspiration & Context

test/playwright/e2e/GridTree.spec.mjs: Serves as a template for tree-specific interactions (expand/collapse, node visibility, hierarchical sorting).
test/playwright/e2e/GridScrollBenchmark.spec.mjs: Serves as a template for performance testing, handling large scrolling areas, and isolating layout jank.

Implementation Steps

Create Test File: Create a new file test/playwright/e2e/GridTreeBigData.spec.mjs.
Basic Initialization & Load Test:
- Navigate to /examples/grid/treeBigData/index.html.
- Wait for the grid to render its initial rows.
- Verify that the ControlsContainer is fully initialized.
Interaction Testing (Expand/Collapse):
- Target a root folder and trigger an expansion.
- Verify that the correct number of child rows are injected into the DOM.
- Verify that the bulk Expand All and Collapse All buttons in the ControlsContainer function correctly without crashing the main thread.
Performance/Scroll Testing:
- Implement vertical and horizontal scroll tests similar to the GridScrollBenchmark.
- Ensure smooth scrolling (native scroll) across a high volume of rows and columns.
Filtering Validation:
- Apply a filter via the ControlsContainer (e.g., firstname).
- Assert that the TreeStore correctly filters the data and that parent folders of matching children remain visible.

tobiu added the enhancement label on Mar 13, 2026, 12:09 PM

tobiu added the ai label on Mar 13, 2026, 12:09 PM

tobiu added the testing label on Mar 13, 2026, 12:09 PM

tobiu assigned to @tobiu on Mar 13, 2026, 12:09 PM

tobiu added parent issue #9461 on Mar 13, 2026, 12:09 PM

tobiu referenced in commit cae1d2a - "#9466 initial e2e setup" on Mar 13, 2026, 1:45 PM

tobiu referenced in commit 0d8bca4 - "test(E2E): Rewrite GridTreeBigData to handle virtual scroll metrics (#9466) on Mar 13, 2026, 2:28 PM

tobiu Mar 13, 2026, 2:29 PM

Input from Gemini 3.1 Pro:

✦ I have committed and pushed the updated E2E tests for the TreeGrid Big Data example.

Changed the test logic to work robustly with virtual scrolling by looking for specific data-record-id changes and structural shifts, rather than exact count assertions for expanded/filtered states.

Handled the sliding ControlsContainer toggling to ensure the controls panel does not obstruct mouse events or go out of bounds.

Augmented the Filtering test to evaluate both positive matches (forcing auto-expansion) and invalid matches (forcing 0 results), testing the persistence of expansion states after clearing the filter.

Applied the Knowledge Base Enhancement Strategy by adding architectural comments to TreeStore.#rebuildKeysAndCount() and the E2E test file itself to guide future tests on virtual scrollers.

tobiu closed this issue on Mar 13, 2026, 2:29 PM