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	9345
title	Final Narrative Arc & Editorial Polish
state	Closed
labels	documentationai
assignees	tobiu
createdAt	Feb 27, 2026, 8:55 PM
updatedAt	Feb 28, 2026, 3:02 AM
githubUrl	https://github.com/neomjs/neo/issues/9345
author	tobiu
commentsCount	1
parentIssue	9339
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Feb 28, 2026, 3:02 AM

Final Narrative Arc & Editorial Polish

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

Closed v12.0.0 documentationai

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

Assemble the final document. Ensure a strong narrative flow emphasizing the "Cyborg Factor". Carefully curate the changelog to distinguish between actual framework bugs and the natural churn of "ironing out new features" built during this cycle, reinforcing that v12 is highly stable.

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

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

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

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

tobiu referenced in commit e3ce244 - "docs: Finalize narrative arc and editorial polish for v12.0.0 release notes (#9345)" on Feb 28, 2026, 3:01 AM

tobiu Feb 28, 2026, 3:02 AM

Input from Gemini 3.1 Pro:

✦ I have significantly restructured and polished the v12.0.0 release notes.

Key improvements:

Narrative Overhaul: Elevated the tone from standard documentation to an aggressive, confident "Velocity Case Study" format.

Terminology Alignment: Enforced the "Application Engine" identity globally, completely removing references to "framework" when describing Neo.mjs.

Philosophical Anchors: Weaved the concepts of Object Permanence and Declarative Everything directly into the TL;DR and AI (Cyborg Factor) sections, contrasting them against the current industry meta of ephemeral rendering and Vibe Coding.

Changelog Curation: Reduced the massive 400+ ticket dump down to the highest-signal structural and architectural changes, removing over 100 minor "noise" tickets (typos, JSDoc, chores) to make the achievement readable.

The final document serves as both a changelog and a definitive RAG-optimized knowledge anchor for future AI interactions.

The changes have been pushed to the dev branch.

tobiu closed this issue on Feb 28, 2026, 3:02 AM