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	8915
title	Refactor GridDragScroll to use unified event handlers
state	Closed
labels	developer-experienceairefactoringperformance
assignees	tobiu
createdAt	Jan 30, 2026, 2:17 PM
updatedAt	Jan 30, 2026, 2:21 PM
githubUrl	https://github.com/neomjs/neo/issues/8915
author	tobiu
commentsCount	1
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Jan 30, 2026, 2:21 PM

Refactor GridDragScroll to use unified event handlers

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

Closed v11.24.0 developer-experienceairefactoringperformance

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

Problem: The newly created Neo.main.addon.GridDragScroll contains significant code duplication between its mouse (onMouseDown, onMouseMove, onMouseUp) and touch (onTouchStart, onTouchMove, onTouchEnd) event handlers. The logic for delta calculation, registration lookup, and drag state management is nearly identical.

Solution: Refactor the addon to use unified event handlers for both input types.

Tasks:

Unified Handlers: Create onDragStart, onDragMove, and onDragEnd methods that handle both MouseEvent and TouchEvent types.
Coordinate Normalization: Implement a helper or internal logic to extract clientX and clientY uniformly from either event type (using event.touches[0] for touch).
Registration Update: Simplify register and unregister to attach these unified listeners based on Neo.config.hasTouchEvents.
Cleanup: Remove the redundant separate handlers.

Benefits:

Reduced file size.
Improved maintainability (single source of truth for drag logic).
easier to extend in the future.

tobiu added the developer-experience label on Jan 30, 2026, 2:17 PM

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

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

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

tobiu referenced in commit 023f6b7 - "refactor: Refactor GridDragScroll to use unified event handlers (#8915)" on Jan 30, 2026, 2:20 PM

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

tobiu Jan 30, 2026, 2:21 PM

Input from Gemini 3 Pro:

✦ I have successfully refactored Neo.main.addon.GridDragScroll to use unified event handlers, significantly reducing code duplication.

Refactoring Details

1. Unified Logic:

Replaced separate onMouseDown/onTouchStart with a single onDragStart.

Replaced separate onMouseMove/onTouchMove with a single onDragMove.

Replaced separate onMouseUp/onTouchEnd with a single onDragEnd.

2. Coordinate Normalization:

Implemented getEventCoordinates(event) to abstract away the differences between MouseEvent (clientX/Y) and TouchEvent (touches[0].clientX/Y).

3. Streamlined Registration:

The register and unregister methods now share the same handler references, with only minor conditional logic to determine which DOM event type (mousedown vs touchstart) to listen for based on Neo.config.hasTouchEvents.

Outcome: The addon is now more concise (removed ~57 lines) and easier to maintain, with a single source of truth for drag logic regardless of the input device. Behavior remains identical to the previous implementation.

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