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	8071
title	Refactor LivePreview to handle multi-window logic internally
state	Closed
labels	enhancementairefactoring
assignees	tobiu
createdAt	Dec 9, 2025, 4:56 PM
updatedAt	Dec 9, 2025, 5:19 PM
githubUrl	https://github.com/neomjs/neo/issues/8071
author	tobiu
commentsCount	1
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Dec 9, 2025, 5:19 PM

Refactor LivePreview to handle multi-window logic internally

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

Closed v11.17.0 enhancementairefactoring

tobiu commented on Dec 9, 2025, 4:56 PM

This refactoring aims to decouple the Neo.code.LivePreview component from the Portal.view.ViewportController.

Scope:

Internalize Logic: Move the onAppConnect and onAppDisconnect logic from ViewportController.mjs directly into LivePreview.mjs.
Worker Events: LivePreview will subscribe directly to Neo.currentWorker events.
Configuration: Add a windowUrl config to LivePreview (default: './childapps/preview/index.html') to allow apps to customize the location of the preview entry point.
Multi-Window Guard: Ensure the pop-out button and event listeners are only active if Neo.config.useSharedWorkers is true.
Cleanup: Remove the PortalPreview specific logic from apps/portal/view/ViewportController.mjs.

Note on Child Apps: This refactor retains the requirement for the embedding application to provide the physical child app files (index.html, app.mjs) to ensure correct worker path resolution in production builds.

tobiu added the enhancement label on Dec 9, 2025, 4:56 PM

tobiu added the ai label on Dec 9, 2025, 4:56 PM

tobiu added the refactoring label on Dec 9, 2025, 4:56 PM

tobiu assigned to @tobiu on Dec 9, 2025, 4:56 PM

tobiu referenced in commit d9e86fc - "Refactor LivePreview to handle multi-window logic internally #8071" on Dec 9, 2025, 5:18 PM

tobiu Dec 9, 2025, 5:19 PM

Input from Gemini 3.0:

✦ I have completed the refactoring to decouple LivePreview from ViewportController.

Changes Implemented:

Logic Internalization: Neo.code.LivePreview now self-manages its multi-window lifecycle. It directly subscribes to Neo.currentWorker connect and disconnect events.

Configuration: Added a windowUrl config to LivePreview (defaults to ./childapps/preview/index.html), allowing for flexible deployment paths.

Clean Separation: Removed all PortalPreview-specific logic and the onAppConnect method from Portal.view.ViewportController.

Feature Guard: The pop-out functionality and event listeners are now strictly conditional on Neo.config.useSharedWorkers.

The component is now portable and reusable across different Neo.mjs applications without requiring a specific controller implementation. The embedding app is only responsible for providing the physical child app files (as referenced by windowUrl) to ensure correct worker path resolution.

tobiu closed this issue on Dec 9, 2025, 5:19 PM