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	8160
title	Decouple and Configure Window Detachment Thresholds in SortZone
state	Closed
labels	enhancementai
assignees	tobiu
createdAt	Dec 27, 2025, 10:00 PM
updatedAt	Mar 30, 2026, 1:32 PM
githubUrl	https://github.com/neomjs/neo/issues/8160
author	tobiu
commentsCount	2
parentIssue	8163
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Mar 30, 2026, 1:32 PM

Decouple and Configure Window Detachment Thresholds in SortZone

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

Closedenhancementai

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

Currently, Neo.draggable.container.SortZone uses the same intersection logic (or similar 50% ratios) for both in-app item sorting (swapping items) and window detachment/re-integration. This limits UX tuning, as users often expect a "tear-off" into a new window to happen sooner (e.g., at 20% overlap) than an item swap.

Goal:

Decouple the window detachment/re-integration thresholds from the standard sorting thresholds.
Introduce specific configs (e.g., detachThreshold: 0.2, reattachThreshold: 0.8).
Ensure onDragMove logic uses the correct threshold for the correct action (sorting vs. window boundary checks).

tobiu added the enhancement label on Dec 27, 2025, 10:00 PM

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

tobiu added parent issue #8163 on Dec 27, 2025, 10:33 PM

tobiu assigned to @tobiu on Dec 28, 2025, 1:07 AM

tobiu referenced in commit 9a7d24f - "Decouple and Configure Window Detachment Thresholds in SortZone #8160 wip" on Dec 28, 2025, 3:14 AM

tobiu referenced in commit 628fb8d - "#8160 wip" on Dec 28, 2025, 2:10 PM

tobiu Dec 28, 2025, 2:11 PM

Input from Gemini:

✦ ### Session Refactoring Summary (Issue #8160)

In this session, we focused on decoupling window detachment thresholds and consolidating the intersection logic.

Key Changes:

SortZone.mjs Refactoring:

Extracted the core intersection and threshold logic into a dedicated checkWindowBoundary(data) method.

Introduced an onWindowDragContinue(intersectionRatio, data) hook, allowing subclasses to react to drag moves that stay within the detached/attached state boundaries.

Consolidated the logic for detachThreshold and reattachThreshold to ensure consistent behavior across all sorting zones.

DashboardSortZone.mjs Alignment:

Removed duplicated boundary check logic in onDragMove, now delegating to super.onDragMove().

Implemented onWindowDragContinue to handle the hand-off to DragCoordinator for remote drag updates when the item is detached.

State Sanitation:

Removed the experimental isReintegrating flag and logic, reverting to a cleaner state machine.

Method Ordering:

Methods have been re-sorted chronologically per project guidelines.

Outcome: The threshold logic is now centralized and correctly handles directionality (inwards vs. outwards) using lastIntersectionRatio. The system is prepared for further investigation into the re-detach behavior after full re-integration.

@github-actions - 2026-03-29T04:13:48Z

This issue is stale because it has been open for 90 days with no activity.

2026-03-29T04:13:49Z @github-actions added the stale label

tobiu removed the stale label on Mar 30, 2026, 1:32 PM

tobiu closed this issue on Mar 30, 2026, 1:32 PM