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	9206
title	Commit Playwright Profiling Infrastructure & DomEvents Optimization
state	Closed
labels	aitestingperformance
assignees	tobiu
createdAt	Feb 18, 2026, 4:07 PM
updatedAt	Feb 18, 2026, 4:10 PM
githubUrl	https://github.com/neomjs/neo/issues/9206
author	tobiu
commentsCount	1
parentIssue	9194
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Feb 18, 2026, 4:10 PM

Commit Playwright Profiling Infrastructure & DomEvents Optimization

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

Closed v12.0.0 aitestingperformance

tobiu commented on Feb 18, 2026, 4:07 PM

Objective

Commit the Playwright Profiling infrastructure and configuration changes established during the investigation of #9194.

Tasks

Playwright Config: Commit the updates to test/playwright/playwright.config.e2e.mjs (memory limit increase).
Profiler Test: Commit test/playwright/e2e/GridProfile.spec.mjs.
DomEvents Optimization: Commit the onScroll throttling optimization in src/main/DomEvents.mjs (16ms).

Rationale

These tools and optimizations are valuable for future performance regression testing and baseline maintenance, even if they didn't solve the specific Desktop 30fps issue.

tobiu added the ai label on Feb 18, 2026, 4:07 PM

tobiu added the testing label on Feb 18, 2026, 4:07 PM

tobiu added the performance label on Feb 18, 2026, 4:07 PM

tobiu added parent issue #9194 on Feb 18, 2026, 4:07 PM

tobiu assigned to @tobiu on Feb 18, 2026, 4:08 PM

tobiu referenced in commit c778cc0 - "feat: Add Grid Profiling E2E test & Optimize DomEvents.onScroll (#9206)" on Feb 18, 2026, 4:09 PM

tobiu Feb 18, 2026, 4:10 PM

Input from Gemini 3 Pro:

✦ I have committed the following changes:

Playwright Config: Increased memory limit for chromium tests to 4GB.

Profiler Test: Added test/playwright/e2e/GridProfile.spec.mjs which runs Main Thread performance traces across Mobile, Laptop, and Desktop viewports.

Optimization: Added a 16ms throttle to DomEvents.onScroll to align Main Thread scroll event processing with 60Hz refreshes, preventing potential event flooding on high-frequency input devices.

These changes provide the infrastructure needed to continue the performance investigation.

tobiu closed this issue on Feb 18, 2026, 4:10 PM