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	9366
title	Chrome Windows Color app
state	Open
labels	bug
assignees	[]
createdAt	Mar 6, 2026, 11:30 AM
updatedAt	Mar 26, 2026, 4:17 PM
githubUrl	https://github.com/neomjs/neo/issues/9366
author	kmunk-klarso
commentsCount	2
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]

Chrome Windows Color app

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

Openbug

kmunk-klarso commented on Mar 6, 2026, 11:30 AM

widget nach rausziehen lässt sind reintegrieren

SergioChan Mar 20, 2026, 7:00 PM

Thanks for reporting this.

I want to work on a fix, but I can��t reliably reproduce from the current description yet. Could you share:

Exact steps/click path that trigger the issue
What behavior you expected vs what actually happened
Browser + OS version (especially Chrome on Windows)
Any console errors/screenshots if available

With that, I can put together a minimal, targeted patch.

tobiu Mar 25, 2026, 5:18 PM

Hi @SergioChan,

if I recall it correctly, Katharina meant this one: https://youtu.be/KIZ1rxRuRcQ

It is definitely still broken here: https://neomjs.com/#/home (even on mac os), and several local changes should have fixed it. well, at least on Mac OS it works again.

In case you want to take a look:

Fork the repo
npm i
npm run build-all
npm run server-start
open http://localhost:8080/apps/portal/#/home or alternatively http://localhost:8080/apps/colors/

What should work:

Drag an in-app widget over the container border, it should transform into a popup window without breaking the drag operation. You can continue to drag it back over the origin-container, and it should transform back into an in-app widget.

What does not work yet:

If you drop the popup window outside the main app. Then start a new drag operation and move the popup window directly back over the main app. This is a planned item for the infinite canvas concept though. gut feeling: around neo v13.

@kmunk-klarso please let us know, in case the ticket was related to something else.

@SergioChan If could validate that this demo now also works on Windows OS locally, this would be of great help. Right now, I don't even have a VM running to test it there.

Best regards, Tobias