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	9518
title	Fix LivePreview incorrect popout URL for subsequent windows (SharedWorkers)
state	Closed
labels	bugai
assignees	tobiu
createdAt	Mar 19, 2026, 1:44 PM
updatedAt	Mar 19, 2026, 3:38 PM
githubUrl	https://github.com/neomjs/neo/issues/9518
author	tobiu
commentsCount	2
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Mar 19, 2026, 3:25 PM

Fix LivePreview incorrect popout URL for subsequent windows (SharedWorkers)

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

Closed v12.1.0 bugai

tobiu commented on Mar 19, 2026, 1:44 PM

The root cause of the initial LivePreview popout bug was that the child app configuration (specifically the appPath) was incorrectly being merged into the global Neo.config via worker.Base's onRegisterNeoConfig method during SharedWorker setups.

The fix involved decoupling the boot sequence from the static global Neo.config while avoiding the constant state 'flapping' that caused the bug:

src/worker/Base.mjs: Hardened to strictly merge the initial window connection data into Neo.config. Child apps' configs are securely kept within Neo.windowConfigs.
src/worker/Manager.mjs: Now explicitly includes windowId: this.windowId in the loadApplication message payload sent to the App worker.
src/worker/App.mjs: onLoadApplication now uses the correct appPath derived from Neo.windowConfigs[data.windowId]. It sets a synchronous Neo.bootingWindowId flag specifically for the duration of the module.onStart() execution tick to pass context down the stack. It also conditionally fetches the theme-map.json only once using a new themeMapFetchStarted flag.
src/controller/Application.mjs: Updated both the construct and beforeSetMainView methods to use the instance's proper this.windowId (inherited via the boot flag) instead of statically falling back to Neo.config.windowId.
src/code/LivePreview.mjs: Updated beforeSetWindowUrl to dynamically access the active window's appPath directly from Neo.windowConfigs[windowId], preventing URL segment duplication (childapps/preview/).
src/component/Circle.mjs, Gallery.mjs, & Helix.mjs: Updated to dynamically retrieve path variables from Neo.windowConfigs in afterSetWindowId to support distinct base paths across multiple active windows.

All changes have been successfully committed and pushed to the dev branch.

tobiu added the bug label on Mar 19, 2026, 1:44 PM

tobiu added the ai label on Mar 19, 2026, 1:44 PM

tobiu referenced in commit da2169f - "fix: LivePreview incorrect popout URL and SharedWorker routing issues (#9518)" on Mar 19, 2026, 3:24 PM

tobiu Mar 19, 2026, 3:24 PM

Input from Gemini 3.1 Pro:

✦ The issue has been fully resolved.

The root cause of the bug expanded beyond just LivePreview URL generation. The core issue was that child applications connecting via SharedWorkers were failing to correctly identify their unique windowId, falling back to the original Portal's windowId during the boot sequence. This caused the new child app's mainView to render into the Portal's DOM (effectively replacing the entire portal app viewport) instead of its own popup window.

The comprehensive fix implements explicit context passing for the boot sequence while decoupling it from the static global Neo.config:

src/worker/Manager.mjs: Now explicitly includes windowId: this.windowId in the loadApplication message payload sent to the App worker.

src/worker/App.mjs: onLoadApplication now uses the correct appPath derived from Neo.windowConfigs[data.windowId]. Crucially, it sets a synchronous Neo.bootingWindowId flag specifically for the duration of the module.onStart() execution tick to pass context down the stack.

src/controller/Application.mjs: Updated both the construct and beforeSetMainView methods to use the instance's proper this.windowId (inherited via the boot flag) instead of statically falling back to Neo.config.windowId.

src/component/Circle.mjs, Gallery.mjs, & Helix.mjs: Updated to dynamically retrieve path variables from Neo.windowConfigs in afterSetWindowId to support distinct base paths across multiple active windows.

All changes have been committed and pushed to the dev branch.

tobiu closed this issue on Mar 19, 2026, 3:25 PM

tobiu Mar 19, 2026, 3:30 PM

The initial LivePreview routing bug and the subsequent multi-window routing regressions have been resolved. The fix involves explicitly passing the windowId during application boot to decouple the boot sequence from the flapping global Neo.config, allowing child applications to accurately resolve their respective configurations directly from Neo.windowConfigs.

tobiu assigned to @tobiu on Mar 19, 2026, 3:38 PM