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	8975
title	Fix Grid Header Drag Proxy for Row Component Architecture
state	Closed
labels	bugai
assignees	tobiu
createdAt	Feb 4, 2026, 1:00 AM
updatedAt	Feb 4, 2026, 1:09 AM
githubUrl	https://github.com/neomjs/neo/issues/8975
author	tobiu
commentsCount	1
parentIssue	8964
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Feb 4, 2026, 1:09 AM

Fix Grid Header Drag Proxy for Row Component Architecture

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

Closed v12.0.0 bugai

tobiu commented on Feb 4, 2026, 1:00 AM

The current implementation of createDragProxy in src/draggable/grid/header/toolbar/SortZone.mjs is broken due to recent refactoring of the Grid component (specifically, the introduction of Neo.grid.Row).

Current Issues:

Styling Loss: The drag proxy no longer retains the correct grid styling (e.g., even/odd row colors) because the proxy structure doesn't match the new row-based DOM structure.
Height Calculation: The proxy height calculation might be incorrect or missing the necessary context.
Data Retrieval: While cell content retrieval partly works for simple columns, it needs to be robustly adapted to fetch data from the new Row components.

Goal:

Update createDragProxy to correctly reconstruct the visual representation of the dragged column.
Ensure the proxy includes the full grid height and proper styling (mimicking the grid body).
Adapt the logic to iterate over Neo.grid.Row instances to extract cell VDOM.
Verify that component-based columns are handled gracefully (or at least don't crash, even if fully cloning them is complex).

Implementation Details:

Iterate over grid.body.items (the Row components) instead of body.getVdomRoot().cn.
Extract the specific cell VDOM matching the dragged column index from each Row.
Reconstruct the VDOM for the proxy to include neo-grid-row classes and styles to maintain visual fidelity during the drag operation.

tobiu added the bug label on Feb 4, 2026, 1:00 AM

tobiu added the ai label on Feb 4, 2026, 1:00 AM

tobiu assigned to @tobiu on Feb 4, 2026, 1:00 AM

tobiu added parent issue #8964 on Feb 4, 2026, 1:01 AM

tobiu referenced in commit 0ee130c - "fix: Update Drag Proxy for Grid Row Components (#8975)" on Feb 4, 2026, 1:08 AM

tobiu Feb 4, 2026, 1:08 AM

Input from Gemini 3 Pro:

✦ Refactored createDragProxy to support the new Neo.grid.Row architecture.

Replaced legacy VDOM traversal (body.getVdomRoot().cn) with component-based iteration (body.items).

Now extracting styling and structure directly from Row component instances.

Current Status: Styling for rows and cells is improved, but SortZone behavior is not fully restored to its previous state. Follow-up tickets will be required to address remaining functional regressions.

tobiu closed this issue on Feb 4, 2026, 1:09 AM