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	9400
title	Performance: O(1) Fast Paths for onScrollCapture getById Traversal
state	Closed
labels	enhancementaiarchitectureperformance
assignees	tobiu
createdAt	Mar 8, 2026, 10:16 PM
updatedAt	Mar 8, 2026, 10:35 PM
githubUrl	https://github.com/neomjs/neo/issues/9400
author	tobiu
commentsCount	1
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Mar 8, 2026, 10:35 PM

Performance: O(1) Fast Paths for onScrollCapture getById Traversal

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

Closed v12.1.0 enhancementaiarchitectureperformance

tobiu commented on Mar 8, 2026, 10:16 PM

Problem: During continuous scrolling of a complex Grid, profiling reveals that VDomUtil.getById and VNodeUtil.getById consume a combined ~7.8% of the App Worker's total CPU time (nearly 700ms in a 1-minute trace).

This overhead is generated by the generic onScrollCapture listeners in src/component/Abstract.mjs and src/component/Base.mjs. For every single scroll event, the framework naively dumps the event target.id into getById(me.vnode, target.id), which forces a full recursive tree traversal, even if the node that is scrolling is the component's root node or its designated content wrapper.

Proposed Solution: Introduce O(1) Fast Paths in onScrollCapture to check the most common scrolling targets before falling back to the expensive deep traversal:

Root Node Check: Does target.id equal me.vnode.id?
Logical Root Check: Does target.id equal me.id? (Essential for components using getVdomRoot wrappers, where the inner node receives me.id).
Items Root Check: Does target.id equal me.getVdomItemsRoot().id?

These three checks will short-circuit practically all internal grid and container scrolling events, completely eliminating the deep recursive getById penalty.

tobiu added the enhancement label on Mar 8, 2026, 10:16 PM

tobiu added the ai label on Mar 8, 2026, 10:16 PM

tobiu added the architecture label on Mar 8, 2026, 10:16 PM

tobiu added the performance label on Mar 8, 2026, 10:16 PM

tobiu referenced in commit 116b8f9 - "perf: O(1) Fast Paths for onScrollCapture getById Traversal (#9400)" on Mar 8, 2026, 10:23 PM

tobiu assigned to @tobiu on Mar 8, 2026, 10:23 PM

tobiu Mar 8, 2026, 10:23 PM

Input from Gemini 3.1 Pro:

✦ Task Completed:

Introduced O(1) fast paths into onScrollCapture in src/component/Abstract.mjs and src/component/Base.mjs.

The framework now checks target.id === me.id, target.id === me.vnode.id, and target.id === me.getVnodeItemsRoot()?.id before falling back to VNodeUtil.getById.

This eliminates the need to recursively crawl massive VDOM structures (like Grids) on every single scroll frame when the node scrolling is the component's main scroll wrapper.

This effectively reclaims the ~7.8% App Worker CPU overhead identified in the performance trace.

tobiu referenced in commit 18444a9 - "docs: Add intent and performance notes to onScrollCapture fast paths (#9400)" on Mar 8, 2026, 10:25 PM

tobiu closed this issue on Mar 8, 2026, 10:35 PM