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	7918
title	Epic: Neo Command Center (Agent OS UI)
state	Closed
labels	epicstaleai
assignees	tobiu
createdAt	Nov 29, 2025, 4:17 PM
updatedAt	Mar 19, 2026, 4:58 AM
githubUrl	https://github.com/neomjs/neo/issues/7918
author	tobiu
commentsCount	2
parentIssue	null
subIssues	7920 Design: Agent Dashboard Layout (Multi-Window Architecture) 7921 Feat: Real-time ''Blackboard'' Visualization 7922 Feat: ''Derailment'' Intervention Interface 7954 Task: Scaffold Agent OS Application 7955 Feat: Implement Agent OS Multi-Window Layout 7956 Feat: Multi-Window Orchestration Baseline 8018 Feat: Implement Drag-to-Popup Dashboard 8019 Bug: isWindowDragging flag stuck after external drop 8021 Refactor AgentOS SCSS: Split Source and Variables 8022 Refactor AgentOS Viewport: Modularize Components 8024 Refactor Intervention View to dedicated Grid Component 8025 Create Custom Theme: Neo Cyberpunk 8031 Fix Grid Header Button Border on Hover 8032 Add Glow and Transition to Cyberpunk Grid Header Buttons 8033 Create InterventionPanel.scss and Fix Selection Contrast 8034 Migrate Intervention Panel Styles and Clean Viewport SCSS 8035 Refine Visual Alignment and Button Typography 8036 Increase Toolbar Padding to 20px
subIssuesCompleted	18
subIssuesTotal	18
blockedBy	[]
blocking	[]
closedAt	Mar 19, 2026, 4:58 AM

Epic: Neo Command Center (Agent OS UI)

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

Closed v12.1.0 epicstaleai

tobiu commented on Nov 29, 2025, 4:17 PM

This epic covers Phase 3 of the Agent OS Roadmap: building the "Killer App" that visualizes and controls the agent swarm. This will be a multi-window Neo.mjs application serving as the "God View" for the digital organization.

Goals

Visual Orchestration: Provide a spatial interface to see active agents, tasks, and status.
Derailment Recovery: Enable "Human-in-the-Loop" intervention when agents get blocked.
Dogfooding: Build the interface using the Neo.mjs framework itself, demonstrating its multi-window capabilities.

Key Deliverables

Dashboard Layout: A multi-window workspace design (Strategy, Swarm, Intervention).
Real-time Visualization: A "Blackboard" component that renders the state of the GitHub Issue swarm.
Intervention UI: A chat-like interface to guide stuck agents.

tobiu added the epic label on Nov 29, 2025, 4:17 PM

tobiu added the ai label on Nov 29, 2025, 4:17 PM

tobiu cross-referenced by #7920 on Nov 29, 2025, 4:19 PM

tobiu added sub-issue #7920 on Nov 29, 2025, 4:21 PM

tobiu added sub-issue #7921 on Nov 29, 2025, 4:22 PM

tobiu added sub-issue #7922 on Nov 29, 2025, 4:22 PM

tobiu assigned to @tobiu on Nov 30, 2025, 7:37 PM

tobiu cross-referenced by #7954 on Nov 30, 2025, 7:39 PM

tobiu added sub-issue #7954 on Nov 30, 2025, 7:39 PM

tobiu added sub-issue #7955 on Nov 30, 2025, 7:42 PM

tobiu added sub-issue #7956 on Nov 30, 2025, 10:00 PM

tobiu added sub-issue #8018 on Dec 4, 2025, 2:15 AM

tobiu added sub-issue #8019 on Dec 4, 2025, 2:30 AM

tobiu added sub-issue #8021 on Dec 4, 2025, 4:45 AM

tobiu added sub-issue #8022 on Dec 4, 2025, 4:45 AM

tobiu added sub-issue #8024 on Dec 4, 2025, 11:49 PM

tobiu added sub-issue #8025 on Dec 5, 2025, 12:37 AM

tobiu added sub-issue #8031 on Dec 5, 2025, 2:02 AM

tobiu added sub-issue #8032 on Dec 5, 2025, 3:07 AM

tobiu added sub-issue #8033 on Dec 5, 2025, 3:19 AM

tobiu added sub-issue #8034 on Dec 5, 2025, 3:43 AM

tobiu added sub-issue #8035 on Dec 5, 2025, 4:03 AM

tobiu added sub-issue #8036 on Dec 5, 2025, 4:28 AM