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	9616
title	Grid Multi-Body: Implement Two-Tier Horizontal Cell Pooling and Scroll Sync
state	Closed
labels	enhancementaigrid
assignees	tobiu
createdAt	Mar 31, 2026, 10:22 PM
updatedAt	Apr 1, 2026, 7:21 PM
githubUrl	https://github.com/neomjs/neo/issues/9616
author	tobiu
commentsCount	1
parentIssue	9486
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Apr 1, 2026, 7:21 PM

Grid Multi-Body: Implement Two-Tier Horizontal Cell Pooling and Scroll Sync

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

Closedenhancementaigrid

tobiu commented on Mar 31, 2026, 10:22 PM

Goal

Implement a performant Two-Tier Horizontal Synchronization architecture for the Multi-Body Grid to support App Worker-side cell buffering and pooling while maintaining zero-jitter visual updates on the Main Thread.

Context

This is a sub-issue for Epic #9486. The current horizontal scroll implementation delegates visuals to the Main Thread but fails to update the App Worker with the necessary scroll deltas to recalculate mountedColumns. Without propagating scrollLeft to the App Worker, horizontal cell pooling (recycling columns) cannot function correctly.

Implementation Plan

Main Thread Addon (Visual Sync): Refactor GridHorizontalScrollSync to manually patch the live DOM left positions of center body cells and the center toolbar in the same rAF loop.
App Worker Sync (Data Virtualization): Add domListeners to the HorizontalScrollbar to route native scroll events to ScrollManager, which will update the respective GridBody components with the new scrollLeft.
VDOM Alignment: Inject data-x into the Row cell configurations. The App Worker will bake in the horizontal offset (columnPosition.x - scrollLeft) to perfectly align its new VDOM structure with the live-patched Main Thread cells, preventing rollback jitter.
Pinning Fix: Update GridRowScrollPinning to apply translateY identically across all active multi-body sections (start/center/end) during vertical scrolling.

tobiu added the enhancement label on Mar 31, 2026, 10:22 PM

tobiu added the ai label on Mar 31, 2026, 10:22 PM

tobiu added the grid label on Mar 31, 2026, 10:22 PM

tobiu added parent issue #9486 on Mar 31, 2026, 10:22 PM

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

tobiu referenced in commit be0fcab - "feat: Implement CSS-based horizontal scroll sync with App Worker data virtualization interception (#9616)" on Apr 1, 2026, 7:21 PM

tobiu Apr 1, 2026, 7:21 PM

Input from Gemini 3.1 Pro (Antigravity):

✦ The two-tier horizontal scroll synchronization has been successfully implemented and merged!

Implementation Details:

Main Thread CSS Synchronization: Utilized transform: translateX(calc(var(--grid-scroll-left, 0px) * -1)) inside Body.scss to automatically perform jitter-free, 60fps horizontal scrolling on all non-locked grid body cells using the CSS variables established by GridHorizontalScrollSync.mjs. This bypasses any need to manually monkey-patch JS ele.style.left properties, resulting in incredible real-time UI performance.

App Worker Interception: Updated ScrollManager.onContainerScroll to natively intercept horizontal scroll events emitted by the HorizontalScrollbar instances and immediately assign bounds and sync via IPC (syncGridBody()). This ensures the App Worker correctly recalculates column physical arrays (mountedColumns) during massive horizontal sweeps without losing state.

E2E Stability: Updated both the base Grid component tests and the DevIndex E2E validation tests. The Horizontal Drag Scroll Moves Cells Optically and Triggers Data Virtualization test now programmatically captures the DOM getBoundingClientRect().left to verify positive pixelShift on the Main Thread.

E2E testing is fully green. Closing this issue.

tobiu closed this issue on Apr 1, 2026, 7:21 PM

tobiu cross-referenced by #9619 on Apr 1, 2026, 7:27 PM