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	9412
title	TreeGrid Component Tests (UI & Interactions)
state	Closed
labels	enhancementaitestinggrid
assignees	tobiu
createdAt	Mar 9, 2026, 12:03 PM
updatedAt	Mar 12, 2026, 12:41 PM
githubUrl	https://github.com/neomjs/neo/issues/9412
author	tobiu
commentsCount	1
parentIssue	9404
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Mar 12, 2026, 12:41 PM

TreeGrid Component Tests (UI & Interactions)

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

Closed v12.1.0 enhancementaitestinggrid

tobiu commented on Mar 9, 2026, 12:03 PM

Goal

Verify the visual rendering, Row Pooling integrity, and DOM event handling of the Tree Grid in a real browser environment.

Details

Rendering & Row Pooling:
- Create a test grid with a TreeStore.
- Verify that expanding a node correctly injects the new rows into the DOM without breaking the GridBody virtual map.
- Verify that aria-rowindex remains gapless and contiguous during expand/collapse operations.
Interactions:
- Simulate real clicks on the .neo-tree-toggle-icon using the neo Playwright fixture.
- Assert that the expand and collapse events are fired correctly on the grid container.
A11y:
- Assert that aria-expanded, aria-level, and aria-setsize are present and correct on the rendered DOM nodes.
Environment:
- Create tests in test/playwright/component/grid/Tree.spec.mjs.

tobiu added the enhancement label on Mar 9, 2026, 12:03 PM

tobiu added the ai label on Mar 9, 2026, 12:03 PM

tobiu added the testing label on Mar 9, 2026, 12:03 PM

tobiu added the grid label on Mar 9, 2026, 12:03 PM

tobiu added parent issue #9404 on Mar 9, 2026, 12:03 PM

tobiu assigned to @tobiu on Mar 9, 2026, 12:11 PM

tobiu referenced in commit 63f8231 - "#9412 more testing assertions" on Mar 12, 2026, 11:58 AM

tobiu referenced in commit c657607 - "#9412 cleanup" on Mar 12, 2026, 12:03 PM

tobiu referenced in commit 4c648c1 - "test(grid): add deep state interaction E2E test for TreeGrid (#9412)" on Mar 12, 2026, 12:41 PM

tobiu Mar 12, 2026, 12:41 PM

Input from Gemini 3.1 Pro:

✦ I have significantly enhanced the E2E test suite for the TreeGrid. The test/playwright/e2e/GridTree.spec.mjs file now includes three robust test cases:

Expand / Collapse node: Validates the visual rendering and Row Pooling integrity during simple expansion and collapse of tree nodes, ensuring classes like is-expanded and is-collapsed are correctly applied and is-leaf does not incorrectly bleed over into recycled components (verifying the fix from #9448).

Sorting TreeStore hierarchically: Simulates clicking on the grid column headers (Name) to sort the underlying TreeStore. It rigorously validates the rendered order of the DOM nodes in both ASC and DESC directions to ensure the hierarchical sorting logic accurately reflects on the screen.

Deep state interactions: A complex sequence involving multiple expand, collapse, and sort operations. It tests whether the tree correctly remembers the expanded states of child nodes when a parent node is collapsed and later expanded again, even when interleaved with sorting operations.

All 3 E2E tests pass reliably.

tobiu closed this issue on Mar 12, 2026, 12:41 PM