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	9073
title	refactor: Ensure Drag & Drop Stability via ''internalId''
state	Closed
labels	airefactoringcore
assignees	tobiu
createdAt	Feb 9, 2026, 11:50 AM
updatedAt	Feb 9, 2026, 1:33 PM
githubUrl	https://github.com/neomjs/neo/issues/9073
author	tobiu
commentsCount	1
parentIssue	9074
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Feb 9, 2026, 1:33 PM

refactor: Ensure Drag & Drop Stability via 'internalId'

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

Closed v12.0.0 airefactoringcore

tobiu commented on Feb 9, 2026, 11:50 AM

Context: Cross-store Drag & Drop (e.g., dragging a User to a Project) can fail if both entities share the same ID (e.g., 1) but come from different stores. With internalId (#9070), every item has a globally unique neo-record-x identifier.

Task: Audit and update the Drag & Drop subsystems to leverage internalId for identifying dragged items.

Requirements:

DragZone: Ensure that when a list/grid item is dragged, the dragData includes the internalId.
DropZone: When dropping, use the internalId to resolve the original record from the source store, eliminating ambiguity.
Proxy: Ensure the drag proxy element uses a stable ID.

Scope:

src/draggable/list/DragZone.mjs
src/draggable/grid/DragZone.mjs
src/draggable/DragZone.mjs

tobiu added the ai label on Feb 9, 2026, 11:50 AM

tobiu added the refactoring label on Feb 9, 2026, 11:50 AM

tobiu added the core label on Feb 9, 2026, 11:50 AM

tobiu cross-referenced by #9074 on Feb 9, 2026, 11:51 AM

tobiu added parent issue #9074 on Feb 9, 2026, 11:52 AM

tobiu referenced in commit 97855cc - "refactor: Ensure Drag & Drop Stability via 'internalId' (#9073)" on Feb 9, 2026, 1:32 PM

tobiu Feb 9, 2026, 1:32 PM

Input from Gemini 3 Pro:

✦ Task Completed: Ensure Drag & Drop Stability via 'internalId'

Objective: Ensure that Drag & Drop operations are robust against the new internalId logic (avoiding PK lookup failures) and fix critical regressions exposed by the refactor.

Key Fixes:

Grid Header Sorting (SortZone.mjs):

Regression Fix: Fixed a critical issue where dragging columns containing heavy components (like OffscreenCanvas in Sparklines) destroyed the content.

Root Cause: onDragEnd called super.onDragEnd (which destroys the proxy) before moving the nodes back to the grid.

Solution: Reordered onDragEnd to restore DOM nodes from the proxy to the grid before initiating proxy destruction.

List Drag & Drop (ListDragZone.mjs):

Robust Lookup: Updated setData to handle internalId correctly.

Logic: It first attempts store.get(recordId) (PK lookup). If that fails, it scans the store for a matching internalId. This ensures drag data is correctly populated even when List.Base eventually switches to using internalId for DOM keys.

Status: Grid Row Drag & Drop does not exist yet, so no changes were required there. The Drag & Drop subsystem is now stable.

tobiu assigned to @tobiu on Feb 9, 2026, 1:32 PM

tobiu closed this issue on Feb 9, 2026, 1:33 PM