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	9339
title	Epic: Draft and Finalize v12.0.0 Release Notes
state	Open
labels	documentationepicai
assignees	tobiu
createdAt	Feb 27, 2026, 8:54 PM
updatedAt	Feb 27, 2026, 8:54 PM
githubUrl	https://github.com/neomjs/neo/issues/9339
author	tobiu
commentsCount	0
parentIssue	null
subIssues	9340 Hero Story: The DevIndex & Data Layer 9341 Hero Story: The Grid Rewrite 9342 Hero Story: Core Architecture Hardening 9343 Extract DevIndex Guides & Mermaid Diagrams 9344 Extract Engineering War Stories (Memory Core) 9345 Final Narrative Arc & Editorial Polish 9322 Docs: Provide empirical Delta Log proof for Grid Row Pooling in v12 Release Notes 9346 Docs: Add Epic Summary to v12 Release Notes Changelog
subIssuesCompleted	7
subIssuesTotal	8
blockedBy	[]
blocking	[]

Epic: Draft and Finalize v12.0.0 Release Notes

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

Open v12.0.0 documentationepicai

tobiu commented on Feb 27, 2026, 8:54 PM

This epic tracks the creation of the Neo.mjs v12.0.0 release notes. We have approximately 400 tickets in scope, representing a massive month of velocity and architectural evolution.

This epic will be broken down into focused sub-tickets to manage the scope, extract technical narratives, and ensure a high-quality final document.

tobiu assigned to @tobiu on Feb 27, 2026, 8:54 PM

tobiu added the documentation label on Feb 27, 2026, 8:54 PM

tobiu added the epic label on Feb 27, 2026, 8:54 PM

tobiu added the ai label on Feb 27, 2026, 8:54 PM

tobiu added sub-issue #9340 on Feb 27, 2026, 8:54 PM

tobiu added sub-issue #9341 on Feb 27, 2026, 8:54 PM

tobiu added sub-issue #9342 on Feb 27, 2026, 8:55 PM

tobiu added sub-issue #9343 on Feb 27, 2026, 8:55 PM

tobiu added sub-issue #9344 on Feb 27, 2026, 8:55 PM

tobiu added sub-issue #9345 on Feb 27, 2026, 8:55 PM

tobiu added sub-issue #9322 on Feb 27, 2026, 8:57 PM

tobiu referenced in commit 94e2949 - "#9339 early stage draft" on Feb 27, 2026, 9:01 PM

tobiu referenced in commit d1bfcef - "#9339: removing unrelated tickets" on Feb 27, 2026, 11:13 PM

tobiu added sub-issue #9346 on Feb 28, 2026, 12:17 AM

tobiu referenced in commit 87edc46 - "docs: Move testing-related items to Testing & Infrastructure section in v12 Release Notes (#9339)" on Feb 28, 2026, 12:22 AM

tobiu referenced in commit 01d8abb - "docs: Fix mermaid syntax error for DOM Pool translates (#9339)" on Feb 28, 2026, 12:46 AM