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	8038
title	Refactor AgentOS Strategy View into StrategyPanel
state	Closed
labels	enhancementairefactoring
assignees	tobiu
createdAt	Dec 6, 2025, 7:50 PM
updatedAt	Dec 6, 2025, 9:37 PM
githubUrl	https://github.com/neomjs/neo/issues/8038
author	tobiu
commentsCount	1
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Dec 6, 2025, 9:37 PM

Refactor AgentOS Strategy View into StrategyPanel

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

Closed v11.17.0 enhancementairefactoring

tobiu commented on Dec 6, 2025, 7:50 PM

Extract the inline Strategy view from apps/agentos/view/Viewport.mjs into a new file apps/agentos/view/StrategyPanel.mjs.

Requirements:

New Class: AgentOS.view.StrategyPanel extending Neo.container.Panel.
Dashboard Container: The main item of this panel should be a Neo.dashboard.Container.
Horizontal Layout: The dashboard should be configured to display items horizontally (e.g., layout: {ntype: 'hbox', align: 'stretch'}).
Cards: Implement the 3 current KPI cards (Velocity, Active Epics, Uptime) as child Panels within the Dashboard.
Drag & Drop: Enable drag & drop for these cards (horizontal resorting) and allow dragging them out to popups.
- Duplicate the DD logic from ViewportController.mjs into a new StrategyPanelController.mjs for now.
SCSS: Refactor the SCSS to move specific strategy styles into resources/scss/theme-cyberpunk/apps/agentos/StrategyPanel.scss.

Current Implementation: The strategy view is currently an inline items config in Viewport.mjs.

Goal: Improve modularity and enable advanced dashboard features for the Strategy view.

tobiu added the enhancement label on Dec 6, 2025, 7:50 PM

tobiu added the ai label on Dec 6, 2025, 7:50 PM

tobiu added the refactoring label on Dec 6, 2025, 7:50 PM

tobiu assigned to @tobiu on Dec 6, 2025, 7:50 PM

tobiu referenced in commit fce09c9 - "Refactor AgentOS Strategy View into StrategyPanel #8038" on Dec 6, 2025, 9:35 PM

tobiu Dec 6, 2025, 9:36 PM

Input from Gemini 2.5 pro:

✦ Refactoring and enhancement of the AgentOS Strategy View is complete.

Key Changes:

Architecture & Modularization:

Extracted the inline Strategy view from Viewport.mjs into a new dedicated class: AgentOS.view.StrategyPanel.

Created a dedicated controller AgentOS.view.StrategyPanelController to handle window management and drag-and-drop logic, mirroring the patterns established in ViewportController.

Dashboard & Layout:

Implemented Neo.dashboard.Container as the core of the StrategyPanel, configured with an hbox layout to display KPI cards horizontally.

Converted the 3 KPI cards (Velocity, Active Epics, Uptime) into child Neo.container.Panel instances.

Drag & Drop Functionality:

Enabled full drag-and-drop support for the KPI cards.

Internal: Cards can be reordered horizontally within the dashboard.

External: Cards can be dragged out of the main window to spawn separate popup windows (using the neo-draggable headers).

Re-integration: Closing a popup or dragging it back seamlessly returns the widget to its original position in the dashboard.

UI & Theming (Cyberpunk):

Refactored SCSS into a dedicated structure file: resources/scss/src/apps/agentos/StrategyPanel.scss.

Design Update: Moved KPI "Topics" (Velocity, etc.) to the panel headers to serve as drag handles.

Visual Polish: Implemented a "monolithic card" aesthetic where the panel header and body share a background color (--agent-bg-panel) to create an "elevated" look against the dark dashboard background. This was achieved by setting internal body backgrounds to transparent and applying styles to the wrapper.

Cleaned up legacy styles in Viewport.scss to prevent conflicts.

Files Created/Modified:

apps/agentos/view/StrategyPanel.mjs (New)

apps/agentos/view/StrategyPanelController.mjs (New)

apps/agentos/view/Viewport.mjs (Updated)

resources/scss/src/apps/agentos/StrategyPanel.scss (New)

resources/scss/src/apps/agentos/Viewport.scss (Updated)

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