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	8350
title	Docs: Rebrand Neo.mjs as an Application Engine in README
state	Closed
labels	documentationenhancementai
assignees	tobiu
createdAt	Jan 6, 2026, 12:18 PM
updatedAt	Jan 6, 2026, 12:34 PM
githubUrl	https://github.com/neomjs/neo/issues/8350
author	tobiu
commentsCount	2
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Jan 6, 2026, 12:30 PM

Docs: Rebrand Neo.mjs as an Application Engine in README

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

Closed v11.19.0 documentationenhancementai

tobiu commented on Jan 6, 2026, 12:18 PM

Reflect the new strategic identity of Neo.mjs as an Application Engine (comparable to Unreal Engine) rather than a traditional UI framework.

Key Themes to Integrate:

Scope: Neo.mjs is an "Application Engine" (Runtime + Tooling), not just a UI library. (Unreal Engine analogy).
Performance: F1 vs Toyota. Purpose-built for speed and precision vs mass-market compromises.
Structure: Lego Technic vs Duplo. Engineered parts for complex machinery vs simple blocks for basic shapes.

Implementation Plan: Apply tiny iterations in sequence to README.md to ensure no content is lost while shifting the narrative.

tobiu added the documentation label on Jan 6, 2026, 12:18 PM

tobiu added the enhancement label on Jan 6, 2026, 12:18 PM

tobiu added the ai label on Jan 6, 2026, 12:18 PM

tobiu assigned to @tobiu on Jan 6, 2026, 12:18 PM

tobiu referenced in commit 66ad6fa - "Docs: Rebrand Neo.mjs as an Application Engine #8350" on Jan 6, 2026, 12:30 PM

tobiu Jan 6, 2026, 12:30 PM

Input from Gemini 3 Pro:

✦ I have successfully updated the README.md to reflect the new "Application Engine" identity, incorporating the "Unreal Engine", "F1 vs Toyota", and "Lego Technic vs Duplo" analogies as requested.

Changes applied:

Header: "The Application Engine for the AI Era".

Introduction: Explicit definition as an Engine (Runtime + Tooling) with the Unreal Engine analogy.

Why Choose Neo: "F1 vs Toyota" analogy for performance.

Batteries Included: "Lego Technic vs Duplo" analogy for runtime permutation.

Neural Link: Added as the 5th pillar of the AI-Native platform.

Key Features: Renamed "Persistent Component Instances" to "Runtime Permutation & Object Permanence".

The README now clearly articulates the "Engine" vision. I will now proceed to align the ROADMAP.md with this new strategic direction in a separate ticket.

tobiu closed this issue on Jan 6, 2026, 12:30 PM

tobiu Jan 6, 2026, 12:34 PM

Input from Gemini 3 Pro:

✦ I have completed the core text rebranding in README.md.

State of the file:

Header/Intro: Defined as "Application Engine" with Unreal Engine analogy.

Why Choose: F1 vs Toyota analogy integrated.

Batteries: Lego Technic vs Duplo analogy integrated.

AI-Native: Neural Link added as the 5th pillar.

Key Features: "Runtime Permutation & Object Permanence" introduced.

Next Steps: The "Architectural Deep Dive" comparison table is now conceptually misaligned (comparing an Engine to Libraries). I will create a follow-up ticket to replace this section with an "Engine Architecture" breakdown (Runtime vs Toolchain vs Assets) instead of patching the existing table.

tobiu referenced in commit 0235420 - "Docs: Rebrand Neo.mjs as an Application Engine #8350" on Jan 6, 2026, 12:34 PM