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	8114
title	Fix Drag-to-Popup Event Routing and Re-integration Logic
state	Closed
labels	bugai
assignees	tobiu
createdAt	Dec 15, 2025, 1:57 PM
updatedAt	Dec 15, 2025, 1:59 PM
githubUrl	https://github.com/neomjs/neo/issues/8114
author	tobiu
commentsCount	1
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Dec 15, 2025, 1:59 PM

Fix Drag-to-Popup Event Routing and Re-integration Logic

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

Closed v11.17.0 bugai

tobiu commented on Dec 15, 2025, 1:57 PM

This ticket covers the fixes required to support seamless drag-to-popup and re-integration (drag-back) workflows, specifically when using DragProxyContainer.

Issues Addressed:

Event Loss: Drag events stopped firing when the dragged component (moved to a proxy outside the dashboard) was no longer in the delegation path of the dashboard listener.
Re-integration Duplication: Moving the widget back to the dashboard/proxy during drag caused VDOM/DOM duplication.
Sorting Glitches: Sorting logic continued to run while the widget was "floating" as a window.

Changes:

src/main/addon/DragDrop.mjs: Updated onDragMove to include dragZoneId in the message payload.
src/manager/DomEvent.mjs: Updated fire to route drag:move/end events directly to the DragZone instance if dragZoneId is present, bypassing DOM bubbling.
apps/agentos/view/StrategyPanelController.mjs:
- Updated onWindowConnect to use removeFromPreviousParent=false (via mainView.add).
- Updated onDragBoundaryEntry to use sortZone.dragProxy.add(widget, true) (silent add) to restore state without VDOM duplication.
- Added guards to onWindowDisconnect.
src/draggable/container/SortZone.mjs: Restored return statements in onDragMove to pause sorting while isWindowDragging is true.

tobiu added the bug label on Dec 15, 2025, 1:57 PM

tobiu added the ai label on Dec 15, 2025, 1:57 PM

tobiu assigned to @tobiu on Dec 15, 2025, 1:57 PM

tobiu referenced in commit a47f091 - "Fix Drag-to-Popup Event Routing and Re-integration Logic #8114" on Dec 15, 2025, 1:58 PM

tobiu Dec 15, 2025, 1:58 PM

Input from Neo Agent:

◆ I have verified that all changes are implemented:

DragDrop.mjs sends dragZoneId.

DomEvent.mjs routes drag: events to the zone directly.

StrategyPanelController.mjs handles silent re-integration and window connect correctly.

SortZone.mjs pauses sorting during window drag.

The functionality is fully restored and enhanced.

tobiu closed this issue on Dec 15, 2025, 1:59 PM