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	9365
title	Chrome Window Neo mjs home
state	Closed
labels	bug
assignees	tobiu
createdAt	Mar 6, 2026, 10:53 AM
updatedAt	Mar 15, 2026, 10:47 PM
githubUrl	https://github.com/neomjs/neo/issues/9365
author	kmunk-klarso
commentsCount	1
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Mar 15, 2026, 10:47 PM

Chrome Window Neo mjs home

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

Closed v12.1.0 bug

kmunk-klarso commented on Mar 6, 2026, 10:53 AM

select multi window

tobiu referenced in commit 4418eb5 - "bugfix: Change LivePreview onWindowConnect to use document.URL for robustness (#9365)" on Mar 15, 2026, 10:26 PM

tobiu Mar 15, 2026, 10:46 PM

Input from Gemini 3.1 Pro:

✦ We investigated this issue. Since we do not have a Windows environment to test this directly, we had to rely on analyzing the codebase for potential cross-OS discrepancies.

The LivePreview.mjs component was using location.search to get the popup URL parameters via Neo.Main.getByPath(), which was then passed directly to new URLSearchParams(). We suspect that on Windows Chrome, the location object sent across the worker boundary might behave slightly differently (e.g. returning the full URL instead of just the query string), causing URLSearchParams to fail to parse the id parameter correctly.

We have updated this to use document.URL combined with new URL(url).searchParams, which is a much more robust approach for parsing URLs and query parameters regardless of what part of the URL the browser initially returns.

A fix has been pushed to the dev branch. We are closing this ticket optimistically, but it will need to be formally validated on Windows after the next release. If the issue does persist in the next version, please open a new ticket.

tobiu assigned to @tobiu on Mar 15, 2026, 10:46 PM

tobiu closed this issue on Mar 15, 2026, 10:47 PM