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	9569
title	Epic: Neo.mjs v12.1 Release Notes
state	Open
labels	documentationepicai
assignees	tobiu
createdAt	Mar 27, 2026, 11:31 AM
updatedAt	Mar 27, 2026, 11:59 AM
githubUrl	https://github.com/neomjs/neo/issues/9569
author	tobiu
commentsCount	0
parentIssue	null
subIssues	9570 Draft Release Notes: TreeGrid & Data Pipeline Architecture 9571 Draft Release Notes: Locked Columns & Value Banding 9572 Draft Release Notes: ScrollSync & Performance 9573 Draft Release Notes: Learning Guides & Minor Features 9574 Draft Release Notes: Generate Full Changelog 9575 Draft Release Notes: Gather Visual Assets 9576 Draft Release Notes: MCP Infrastructure & Security 9577 Draft Release Notes: Storytelling & Narrative Arc
subIssuesCompleted	8
subIssuesTotal	8
blockedBy	[]
blocking	[]

Epic: Neo.mjs v12.1 Release Notes

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

Open v12.1.0 documentationepicai

tobiu commented on Mar 27, 2026, 11:31 AM

This epic tracks the creation of the Neo.mjs v12.1 release notes. v12.1 encompasses 178 resolved tickets (excluding stale/invalid items), featuring major structural upgrades to the Grid and Data layers.

Proposed Sub-Tasks

Task 1: Draft TreeGrid & Data Pipeline Architecture Section (Focuses on TreeStore, normalizer, and full CRUD hierarchical data mutations).
Task 2: Draft ScrollSync, Locked Columns & Grid Performance Section (Focuses on mobile/desktop 2-way binding, optical pinning, and mathematical column layouts).
Task 3: Draft Core Engine Learning Guides Section & Minor Features (Highlights the new workshop guides and smaller enhancements).
Task 4: Compilation, Proofreading, and Publication (Generating the final markdown file with the full changelog).

tobiu added the documentation label on Mar 27, 2026, 11:31 AM

tobiu added the epic label on Mar 27, 2026, 11:31 AM

tobiu added the ai label on Mar 27, 2026, 11:31 AM

tobiu cross-referenced by #9570 on Mar 27, 2026, 11:34 AM

tobiu added sub-issue #9570 on Mar 27, 2026, 11:37 AM

tobiu cross-referenced by #9571 on Mar 27, 2026, 11:37 AM

tobiu added sub-issue #9571 on Mar 27, 2026, 11:37 AM

tobiu cross-referenced by #9572 on Mar 27, 2026, 11:39 AM

tobiu added sub-issue #9572 on Mar 27, 2026, 11:40 AM

tobiu cross-referenced by #9573 on Mar 27, 2026, 11:40 AM

tobiu added sub-issue #9573 on Mar 27, 2026, 11:42 AM

tobiu cross-referenced by #9574 on Mar 27, 2026, 11:44 AM

tobiu cross-referenced by #9575 on Mar 27, 2026, 11:44 AM

tobiu added sub-issue #9574 on Mar 27, 2026, 11:44 AM

tobiu added sub-issue #9575 on Mar 27, 2026, 11:44 AM

tobiu cross-referenced by #9576 on Mar 27, 2026, 11:58 AM

tobiu added sub-issue #9576 on Mar 27, 2026, 11:58 AM

tobiu assigned to @tobiu on Mar 27, 2026, 11:59 AM

tobiu added sub-issue #9577 on Mar 27, 2026, 12:15 PM