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	8039
title	Fix drag proxy styling for StrategyPanel KPI cards
state	Closed
labels	bugdesign
assignees	tobiu
createdAt	Dec 6, 2025, 9:43 PM
updatedAt	Dec 6, 2025, 9:52 PM
githubUrl	https://github.com/neomjs/neo/issues/8039
author	tobiu
commentsCount	1
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Dec 6, 2025, 9:52 PM

Fix drag proxy styling for StrategyPanel KPI cards

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

Closed v11.17.0 bugdesign

tobiu commented on Dec 6, 2025, 9:43 PM

Update dragProxyExtraCls in apps/agentos/view/StrategyPanel.mjs to ['agent-panel-strategy', 'neo-panel'] to ensure correct styling during drag operations.

Additionally, investigate and fix the issue where the drag proxy renders with an unwanted additional border.

Scope:

Verify the dragProxyExtraCls change.
Debug the drag proxy DOM structure and styles to identify the source of the extra border.
Adjust SCSS in resources/scss/src/apps/agentos/StrategyPanel.scss or related files to remove the unwanted border on the proxy.

tobiu added the bug label on Dec 6, 2025, 9:43 PM

tobiu added the design label on Dec 6, 2025, 9:43 PM

tobiu assigned to @tobiu on Dec 6, 2025, 9:43 PM

tobiu referenced in commit 8a5bab5 - "Fix drag proxy styling for StrategyPanel KPI cards #8039" on Dec 6, 2025, 9:52 PM

tobiu closed this issue on Dec 6, 2025, 9:52 PM

tobiu Dec 6, 2025, 9:52 PM

Input from Gemini 2.5 pro:

✦ Fixed the drag proxy styling issue for the StrategyPanel.

Changes:

StrategyPanel.mjs: Confirmed dragProxyExtraCls is set to ['agent-panel-strategy', 'neo-panel']. This ensures the drag proxy (which wraps the dragged item) inherits the necessary CSS context so that nested selectors like .agent-panel-strategy .agent-kpi-card-panel continue to apply.

StrategyPanel.scss: Added a specific rule for &.neo-dragproxy to remove the default border. This prevents the "double border" effect where both the proxy wrapper (which is now a .neo-panel) and the dragged item (the KPI card) would render borders.

Outcome: Dragging KPI cards now correctly renders the card with its original styling and no unwanted artifacts.