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	8161
title	Refine Cross-Window Drag Intersection to Target SortZone Rect
state	Closed
labels	enhancementai
assignees	tobiu
createdAt	Dec 27, 2025, 10:06 PM
updatedAt	Dec 28, 2025, 1:07 AM
githubUrl	https://github.com/neomjs/neo/issues/8161
author	tobiu
commentsCount	1
parentIssue	8163
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Dec 28, 2025, 1:07 AM

Refine Cross-Window Drag Intersection to Target SortZone Rect

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

Closed v11.18.0 enhancementai

tobiu commented on Dec 27, 2025, 10:06 PM

Currently, DragCoordinator triggers a remote drag operation as soon as the mouse enters a target window that has a registered SortZone. It fails to verify if the drag actually intersects with the specific SortZone container within that window.

Current Behavior:

Window.getWindowAt(screenX, screenY) identifies the target window.
DragCoordinator checks if this window is in the registry.
If yes, it immediately delegates to targetSortZone.onRemoteDragMove.

Impact: Dragging an item into a window's blank space, headers, or even DevTools area (if passing getWindowAt) prematurely triggers the dashboard placeholder logic and proxy creation.

Goal: Update DragCoordinator (or delegate to SortZone) to verify that the drag coordinates (or proxy rect) actually intersect with the target SortZone's ownerRect before initiating the remote drag sequence. This ensures the "drop target" effect only activates when visually appropriate.

tobiu added the enhancement label on Dec 27, 2025, 10:06 PM

tobiu added the ai label on Dec 27, 2025, 10:06 PM

tobiu added parent issue #8163 on Dec 27, 2025, 10:33 PM

tobiu assigned to @tobiu on Dec 28, 2025, 12:53 AM

tobiu referenced in commit 711a59b - "Neo.manager.DragCoordinator: Refactor onDragMove for clarity and efficient early returns - #8161" on Dec 28, 2025, 1:03 AM

tobiu Dec 28, 2025, 1:03 AM

Input from gemini:

✦ I have implemented the enhanced intersection logic for cross-window drag operations.

Key Changes:

Neo.draggable.dashboard.SortZone:

Added acceptsRemoteDrag(localX, localY): This method performs a precise point-in-rect check against the dashboard's ownerRect. It handles lazy fetching of the DOM rect if it's not already cached, ensuring the first interaction is handled correctly (albeit asynchronously for the first frame).

Neo.manager.DragCoordinator:

Refactored onDragMove to use this new validation method.

Crucially, it now waits for acceptsRemoteDrag to return true before suspending the source window drag (closing the popup). This prevents the "disappearing item" issue when dragging over window headers or empty space.

Cleaned up the control flow to use early returns, removing deeply nested else blocks.

This ensures that the "drop target" effect and the handover of control only happen when the user clearly intends to drop onto a valid dashboard area.

tobiu closed this issue on Dec 28, 2025, 1:07 AM