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	8163
title	Cross-Window Drag & Drop Refinement & Topology
state	Open
labels	epicno auto closeaiarchitecture
assignees	tobiu
createdAt	Dec 27, 2025, 10:26 PM
updatedAt	Mar 28, 2026, 6:56 AM
githubUrl	https://github.com/neomjs/neo/issues/8163
author	tobiu
commentsCount	1
parentIssue	null
subIssues	8160 Decouple and Configure Window Detachment Thresholds in SortZone 8161 Refine Cross-Window Drag Intersection to Target SortZone Rect 8162 Fix Layout Corruption in Target Dashboard on Remote Drag Exit 8164 Enhance Neo.manager.Window to Track Full Window Geometry 8165 Implement Configurable Theme Inheritance for Dragged Items 8166 Implement Cross-Window Drop Validation and Topology Rules 8167 Harden Return Trip Logic for Detached Items
subIssuesCompleted	3
subIssuesTotal	7
blockedBy	[]
blocking	[]

Cross-Window Drag & Drop Refinement & Topology

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

Openepicno auto closeaiarchitecture

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

This epic tracks the advanced refinement and functional expansion of the Cross-Window Drag & Drop system ("Infinite Canvas").

Scope:

Theming Strategy:
- Implement configurable behavior for dragged items: themeMode: 'adapt' | 'retain'.
- Ensure items dropped into a different app/window correctly adopt (or resist) the target's theme.
Topology & Validation (Sender/Receiver Rules):
- Enhance SortZone validation to support asymmetric flows (e.g., Inner Dashboard -> Main Dashboard allowed, but Main -> Inner blocked).
- Implement allowDrop(draggedItem, sourceZone) hooks.
"Return Trip" Robustness (A -> B -> A):
- Verify and harden the logic for dragging an item out of Window A, hovering Window B, and returning to Window A.
- Ensure state tracking (detachedItems) remains consistent and the original dashboard correctly reclaims its item without duplication or state loss.
Architecture & Documentation:
- Review DragCoordinator responsibility (is it doing too much visual calculation?).
- Comprehensive JSDoc cleanup across SortZone, DashboardSortZone, and DragCoordinator.

tobiu added the epic label on Dec 27, 2025, 10:26 PM

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

tobiu added the architecture label on Dec 27, 2025, 10:26 PM

tobiu added sub-issue #8160 on Dec 27, 2025, 10:33 PM

tobiu added sub-issue #8161 on Dec 27, 2025, 10:33 PM

tobiu added sub-issue #8162 on Dec 27, 2025, 10:33 PM

tobiu added sub-issue #8164 on Dec 27, 2025, 10:33 PM

tobiu added sub-issue #8165 on Dec 27, 2025, 10:33 PM

tobiu added sub-issue #8166 on Dec 27, 2025, 10:33 PM

tobiu added sub-issue #8167 on Dec 27, 2025, 10:33 PM

tobiu assigned to @tobiu on Dec 27, 2025, 11:48 PM

tobiu removed the stale label on Mar 28, 2026, 6:56 AM

tobiu added the no auto close label on Mar 28, 2026, 6:56 AM