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	8914
title	Consolidate Grid Touch Scrolling into Main Thread Addon
state	Closed
labels	enhancementairefactoringarchitectureperformance
assignees	tobiu
createdAt	Jan 30, 2026, 2:03 PM
updatedAt	Jan 30, 2026, 2:14 PM
githubUrl	https://github.com/neomjs/neo/issues/8914
author	tobiu
commentsCount	1
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Jan 30, 2026, 2:14 PM

Consolidate Grid Touch Scrolling into Main Thread Addon

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

Closed v11.24.0 enhancementairefactoringarchitectureperformance

tobiu commented on Jan 30, 2026, 2:03 PM

Problem: Currently, Neo.grid.ScrollManager handles touch scrolling logic (lastTouch positions, owner tracking) inside the App Worker, causing unnecessary cross-worker messaging and latency. Meanwhile, mouse scrolling has been successfully moved to the Neo.main.addon.GridDragScroll for superior performance.

Solution: Consolidate all drag-to-scroll logic (both mouse and touch) into the GridDragScroll Main Thread Addon. This will make the addon the "single source of truth" for grid scrolling interactions.

Architecture Changes:

Refactor Neo.main.addon.GridDragScroll:
- Implement touchstart, touchmove, touchend handlers.
- In register(), detect Neo.config.hasTouchEvents.
- If touch enabled: Attach touch listeners (passive: false, capture: true) instead of mouse listeners.
- Unified logic: Route both input types to the same delta tracking and scrolling implementation.
- Control: Use preventDefault() on touch moves to replace native scrolling with precise 1:1 drag-scrolling.
Cleanup Neo.grid.ScrollManager:
- Remove all mobile-specific logic (lastTouchX, lastTouchY, touchMoveOwner).
- Remove touchcancel and touchend listeners from construct.
- Remove the hasTouchEvents guard from updateDragScrollAddon to enable the addon for all environments.

Benefits:

Performance: Zero-latency touch scrolling by avoiding App Worker round-trips.
Maintainability: Centralized scrolling logic in one place.
Consistency: Identical behavior across desktop and mobile.

tobiu added the enhancement label on Jan 30, 2026, 2:03 PM

tobiu added the ai label on Jan 30, 2026, 2:03 PM

tobiu added the refactoring label on Jan 30, 2026, 2:03 PM

tobiu added the architecture label on Jan 30, 2026, 2:03 PM

tobiu added the performance label on Jan 30, 2026, 2:03 PM

tobiu referenced in commit 374c1eb - "enhancement: Consolidate Grid Touch Scrolling into Main Thread Addon (#8914)" on Jan 30, 2026, 2:13 PM

tobiu assigned to @tobiu on Jan 30, 2026, 2:14 PM

tobiu Jan 30, 2026, 2:14 PM

Input from Gemini 3 Pro:

✦ I have successfully consolidated the grid touch scrolling logic into the Neo.main.addon.GridDragScroll addon.

Changes Implemented

1. Main Thread Addon (src/main/addon/GridDragScroll.mjs)

Touch Support: Implemented touchstart, touchmove, and touchend handlers.

Unified Logic: The addon now acts as the single source of truth for all drag scrolling.

In register(): It checks Neo.config.hasTouchEvents.

Mobile: Attaches touch listeners (passive: false, capture: true). Uses preventDefault() on touchmove to replace native scrolling with precise, zero-latency drag scrolling.

Desktop: Attaches mouse listeners as before.

Documentation: Updated class JSDoc to reflect the dual support.

2. ScrollManager Refactor (src/grid/ScrollManager.mjs)

Cleanup: Removed all legacy App Worker-side touch tracking (lastTouchX, lastTouchY, touchMoveOwner) and listeners.

Simplification: onBodyScroll and onContainerScroll are now purely for syncing state, with no drag logic.

Renaming: Renamed mouseDragScroll_ to dragScroll_ to reflect the broader scope.

Registration: The updateDragScrollAddon method now unconditionally delegates to the addon, allowing the addon to decide which listeners to attach based on the environment.

Outcome

This architecture change eliminates the overhead of passing high-frequency touch events between the Main Thread and App Worker. Grid scrolling on mobile devices is now handled directly in the Main Thread, resulting in zero-latency performance comparable to native scrolling, while maintaining the exact same logic and behavior as the desktop mouse drag.

tobiu closed this issue on Jan 30, 2026, 2:14 PM