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	9585
title	Bug: LivePreview popout windowUrl generates incorrectly in dist environments
state	Closed
labels	bugai
assignees	tobiu
createdAt	Mar 27, 2026, 3:31 PM
updatedAt	Mar 27, 2026, 8:45 PM
githubUrl	https://github.com/neomjs/neo/issues/9585
author	tobiu
commentsCount	1
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Mar 27, 2026, 4:09 PM

Bug: LivePreview popout windowUrl generates incorrectly in dist environments

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

Closed v12.1.0 bugai

tobiu commented on Mar 27, 2026, 3:31 PM

Resolving the webpack basePath against location.href inside dist/development generates an incorrect absolute URL for windowUrl because the AppWorker is only 2 folders deep, whereas the HTML document is 4 folders deep, resulting in a 404 for MicroLoader.mjs.

We should return the relative URL directly and allow window.open natively to resolve it against the main thread's HTML document path. We also need to use Neo.windowConfigs?.[this.windowId] || Neo.config for basePath and useSharedWorkers instead of reading the global Neo.config.

tobiu added the bug label on Mar 27, 2026, 3:31 PM

tobiu added the ai label on Mar 27, 2026, 3:31 PM

tobiu referenced in commit 12b701f - "fix(code): Delete beforeSetWindowUrl manual resolution to leverage native browser relative URLs (#9585)" on Mar 27, 2026, 4:09 PM

tobiu Mar 27, 2026, 4:09 PM

Input from Gemini 3.1 Pro (Antigravity):

✦ Fix implemented natively via commit 12b701ff8. The manual beforeSetWindowUrl string-math logic has been deleted.

We've confirmed that without this method, the Main thread evaluates relative URLs inherently based on the true physical window location, completely bypassing the SharedWorker basePath mapping complexities that caused the environment-stripping anomalies in dist/development. Initial macOS testing confirms that pop-outs from both the Home and Learn app routes resolve flawlessly.

To guarantee no recursive popout regressions or hidden OS edge cases resurface from the original implementation reason (#8074), an expansive review matrix has been scheduled in Analysis Ticket #9586.

tobiu closed this issue on Mar 27, 2026, 4:09 PM

tobiu assigned to @tobiu on Mar 27, 2026, 8:45 PM