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	8034
title	Migrate Intervention Panel Styles and Clean Viewport SCSS
state	Closed
labels	airefactoring
assignees	tobiu
createdAt	Dec 5, 2025, 3:43 AM
updatedAt	Dec 5, 2025, 3:47 AM
githubUrl	https://github.com/neomjs/neo/issues/8034
author	tobiu
commentsCount	1
parentIssue	7918
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Dec 5, 2025, 3:47 AM

Migrate Intervention Panel Styles and Clean Viewport SCSS

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

Closed v11.16.0 airefactoring

tobiu commented on Dec 5, 2025, 3:43 AM

Migrate the remaining intervention panel styles from apps/agentos/Viewport.scss to apps/agentos/InterventionPanel.scss and clean up obsolete code.

Tasks:

Migrate: Move the specific panel styling (header colors, borders) from .agent-panel-intervention in Viewport.scss to InterventionPanel.scss.
Cleanup: Remove the obsolete .agent-terminal, .agent-log-entry, and .agent-log-timestamp styles from Viewport.scss as these elements no longer exist (replaced by Grid).
Refactor: Ensure the migrated styles use the new CSS variables where appropriate.

Goal: Consolidate all intervention-related styling into its dedicated SCSS file and remove dead code.

tobiu added the ai label on Dec 5, 2025, 3:43 AM

tobiu added the refactoring label on Dec 5, 2025, 3:43 AM

tobiu assigned to @tobiu on Dec 5, 2025, 3:43 AM

tobiu added parent issue #7918 on Dec 5, 2025, 3:43 AM

tobiu referenced in commit 7636f3c - "Migrate Intervention Panel Styles and Clean Viewport SCSS #8034" on Dec 5, 2025, 3:47 AM

tobiu Dec 5, 2025, 3:47 AM

Input from Gemini 2.5 pro:

✦ I have successfully migrated the Intervention Panel styling and cleaned up the Viewport SCSS.

Changes:

Migration: Moved panel-specific styles (background, borders, header accents) from Viewport.scss to resources/scss/src/apps/agentos/InterventionPanel.scss.

Cleanup: Removed the obsolete .agent-terminal and related log entry styles from Viewport.scss.

Refactoring: The migrated styles now correctly use the app-specific CSS variables (--agent-bg-panel, --agent-accent-intervention), ensuring they respond to the theme mapping.

The codebase is now cleaner and properly modularized.

tobiu closed this issue on Dec 5, 2025, 3:47 AM