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	9470
title	Fix Grid Drag Scrolling Regression
state	Closed
labels	bugaigrid
assignees	tobiu
createdAt	Mar 14, 2026, 11:45 AM
updatedAt	Mar 14, 2026, 11:46 AM
githubUrl	https://github.com/neomjs/neo/issues/9470
author	tobiu
commentsCount	1
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Mar 14, 2026, 11:46 AM

Fix Grid Drag Scrolling Regression

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

Closed v12.1.0 bugaigrid

tobiu commented on Mar 14, 2026, 11:45 AM

Description

Drag-to-scroll inside the Grid body was broken (both vertically and horizontally).

Root Cause

A regression occurred due to an ID mismatch and tight coupling between GridDragScroll and ScrollSync. GridDragScroll attempted to manually orchestrate ScrollSync to avoid ping-pong loops, but used the ScrollManager ID instead of the VerticalScrollbar ID, causing the DOM updates to silently fail.

Resolution

Removed the explicit ScrollSync coupling from GridDragScroll.

GridDragScroll now mutates scrollTop and scrollLeft natively on the target elements.
This allows the browser to fire standard scroll events.
ScrollSync catches these events and handles its own "ping-pong" lock logic via its coordinatingNodes mechanism, synchronizing the scrollbar perfectly without needing manual orchestration from the drag addon.

tobiu added the bug label on Mar 14, 2026, 11:45 AM

tobiu added the ai label on Mar 14, 2026, 11:45 AM

tobiu added the grid label on Mar 14, 2026, 11:45 AM

tobiu referenced in commit 0134c14 - "Fix Grid Drag Scrolling Regression (#9470)" on Mar 14, 2026, 11:45 AM

tobiu Mar 14, 2026, 11:46 AM

Input from Gemini 3.1 Pro:

✦ The changes have been pushed successfully. Drag-to-scroll functionality is now fully decoupled from ScrollSync awareness and leverages native scroll events, allowing ScrollSync's internal locking to handle the "ping-pong" prevention naturally.

tobiu assigned to @tobiu on Mar 14, 2026, 11:46 AM

tobiu closed this issue on Mar 14, 2026, 11:46 AM