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	8116
title	SortZone: Ensure Drag Proxy cleanup on window drag drop
state	Closed
labels	bugai
assignees	tobiu
createdAt	Dec 15, 2025, 2:49 PM
updatedAt	Dec 19, 2025, 11:28 AM
githubUrl	https://github.com/neomjs/neo/issues/8116
author	tobiu
commentsCount	2
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Dec 19, 2025, 11:28 AM

SortZone: Ensure Drag Proxy cleanup on window drag drop

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

Closed v11.17.0 bugai

tobiu commented on Dec 15, 2025, 2:49 PM

When a drag operation ends in a "window drag" (drop to popup), the drag proxy in the main window persists (hidden) instead of being removed. Ensure onDragEnd correctly cleans up the proxy without destroying the moved component.

tobiu added the bug label on Dec 15, 2025, 2:49 PM

tobiu added the ai label on Dec 15, 2025, 2:49 PM

tobiu Dec 15, 2025, 2:51 PM

Input from Neo Agent:

◆ Investigation Plan for Next Session:

Trace onDragEnd Execution: Add logs to SortZone.onDragEnd to confirm it runs to completion and calls me.dragEnd(data).

Verify destroyDragProxy: Confirm DragZone.destroyDragProxy is called and executes Neo.applyDeltas to remove the proxy node.

Check for Errors: Look for unhandled exceptions that might interrupt the cleanup flow.

Validate Node Removal: Why does the DOM dump show the proxy still exists? Is the removeNode delta failing or targeting the wrong window/ID?

This seems to be a cleanup failure specifically when the restoreDOM block is skipped.

tobiu assigned to @tobiu on Dec 19, 2025, 10:59 AM

tobiu referenced in commit bc1705d - "SortZone: Ensure Drag Proxy cleanup on window drag drop #8116" on Dec 19, 2025, 11:26 AM

tobiu Dec 19, 2025, 11:27 AM

Input from Gemini:

✦ The issue has been resolved.

Root Cause: The drag:end event sent from src/main/addon/DragDrop.mjs to the App worker did not include the dragZoneId. This caused Neo.manager.DomEvent to fail to route the event to the correct DragZone instance when the event target was outside the component's DOM hierarchy (e.g., when dropping into a new window/popup).

Fix: Updated src/main/addon/DragDrop.mjs to explicitly include dragZoneId in the drag:end message payload, mirroring the behavior of drag:move. This ensures onDragEnd is correctly called on the SortZone, allowing the cleanup logic to execute.

tobiu closed this issue on Dec 19, 2025, 11:28 AM