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	9341
title	Hero Story: The Grid Rewrite
state	Closed
labels	documentationai
assignees	tobiu
createdAt	Feb 27, 2026, 8:54 PM
updatedAt	Feb 28, 2026, 12:07 AM
githubUrl	https://github.com/neomjs/neo/issues/9341
author	tobiu
commentsCount	2
parentIssue	9339
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Feb 28, 2026, 12:07 AM

Hero Story: The Grid Rewrite

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

Closed v12.0.0 documentationai

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

Draft the section covering `Neo.grid.Row`, cell pooling, and the core performance metrics. Emphasize that despite the massive changes, the Grid is a drop-in replacement with zero migration effort for existing apps.

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 ai label on Feb 27, 2026, 8:54 PM

tobiu added parent issue #9339 on Feb 27, 2026, 8:54 PM

tobiu referenced in commit d24d32d - "docs(release-notes): Update Hero Story 2 for Grid Rewrite (#9341)" on Feb 27, 2026, 11:24 PM

tobiu Feb 27, 2026, 11:24 PM

Input from Gemini 3.1 Pro:

✦ Hero Story 2 for the Grid Rewrite has been drafted, expanding on the core architectural shifts, component-based rows, Full Pool Rendering, zero DOM mutations, and the GridDragScroll main-thread addon. The changes have been pushed to the dev branch.

tobiu referenced in commit 1f34bc2 - "docs(release-notes): Enhance Hero Story 2 with architecture diagram and zero-allocation details (#9341)" on Feb 27, 2026, 11:26 PM

tobiu referenced in commit 7daf8cb - "docs(release-notes): Move Performance Theater section from Hero Story 2 to Hero Story 1 (#9341)" on Feb 27, 2026, 11:31 PM

tobiu referenced in commit 2ef3581 - "docs(release-notes): Accurately describe the Zombie Canvas issue in Hero Story 2 (#9341)" on Feb 27, 2026, 11:39 PM

tobiu referenced in commit d6faae7 - "docs(release-notes): Add Surgical DOM Move to Hero Story 2 (#9341)" on Feb 27, 2026, 11:41 PM

tobiu referenced in commit bf3eeaa - "docs(release-notes): Enhance delta log proof with component column granularity (#9341)" on Feb 27, 2026, 11:50 PM

tobiu referenced in commit f5b3f2f - "docs(release-notes): Add Zero-Latency Scrolling terminology to Hero Story 2 (#9341)" on Feb 27, 2026, 11:52 PM

tobiu referenced in commit b77719a - "docs(release-notes): Refine VDOM lifecycle shift explanation to clarify Main Thread deltas (#9341)" on Feb 28, 2026, 12:03 AM

tobiu Feb 28, 2026, 12:07 AM

Completed drafting and refining Hero Story 2: The Grid Rewrite. Added deep architectural details regarding Row Pooling, Fixed-DOM-Order, Surgical DOM Moves, and VDOM Lifecycle shifts.

tobiu closed this issue on Feb 28, 2026, 12:07 AM