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	9050
title	Perf: Optimize DomAccess.syncAligns to avoid scroll thrashing
state	Closed
labels	aiperformancecore
assignees	tobiu
createdAt	Feb 8, 2026, 5:27 PM
updatedAt	Feb 8, 2026, 5:29 PM
githubUrl	https://github.com/neomjs/neo/issues/9050
author	tobiu
commentsCount	1
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Feb 8, 2026, 5:29 PM

Perf: Optimize DomAccess.syncAligns to avoid scroll thrashing

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

Closed v12.0.0 aiperformancecore

tobiu commented on Feb 8, 2026, 5:27 PM

Neo.main.DomAccess.syncAligns triggers a full realignment cycle on every scroll event. This can cause significant layout thrashing (performance "hammering"), especially when scrolling inside a floating container (like a Picker's list) that is itself aligned to another element.

Goal: Optimize syncAligns to filter scroll events. It should only trigger re-alignment if the scrolling element is an ancestor of the alignment target or the constraint element. If the scroll event originates from within the aligned component itself (or an unrelated container), the alignment logic should be skipped.

Implementation Plan:

Modify syncAligns in src/main/DomAccess.mjs.
Check if the event type is scroll.
If it is, verify if the event.target contains the align.targetElement or align.constrainToElement.
If neither is contained, return early and skip align().

This will prevent unnecessary calculations and DOM read/writes during scrolling interactions within floating components.

tobiu added the ai label on Feb 8, 2026, 5:27 PM

tobiu added the performance label on Feb 8, 2026, 5:27 PM

tobiu added the core label on Feb 8, 2026, 5:27 PM

tobiu referenced in commit d79dbae - "perf: Optimize DomAccess.syncAligns to avoid scroll thrashing (#9050)" on Feb 8, 2026, 5:28 PM

tobiu Feb 8, 2026, 5:29 PM

Input from Gemini 3 Pro:

✦ I have implemented the optimization in src/main/DomAccess.mjs.

The syncAligns method now checks if the event type is scroll. If it is, and the target is not the document/window, it verifies if the scroll target contains either the align.targetElement or the align.constrainToElement.

If the scroll target is unrelated (e.g., scrolling inside the picker's own content), the re-alignment logic is skipped. This effectively stops the layout thrashing loop.

Merged in commit d79dbae23.

tobiu assigned to @tobiu on Feb 8, 2026, 5:29 PM

tobiu closed this issue on Feb 8, 2026, 5:29 PM