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	8575
title	Create Guide: Declarative Config Merging & Structural Injection Pattern
state	Closed
labels	documentationenhancementai
assignees	tobiu
createdAt	Jan 12, 2026, 3:45 AM
updatedAt	Jan 12, 2026, 3:51 AM
githubUrl	https://github.com/neomjs/neo/issues/8575
author	tobiu
commentsCount	2
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Jan 12, 2026, 3:51 AM

Create Guide: Declarative Config Merging & Structural Injection Pattern

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

Closed v11.20.0 documentationenhancementai

tobiu commented on Jan 12, 2026, 3:45 AM

Create a new comprehensive guide learn/guides/fundamentals/DeclarativeConfigMerging.md explaining the "Structural Injection Pattern" and the native mergeFrom feature.

Topics to cover:

The Problem: Challenges with deep inheritance and configuring nested components (the "prop drilling" equivalent in class-based container hierarchies).
The Solution: Declarative Config Merging using mergeFrom.
Core Concepts:
- [isDescriptor]: true and merge: 'deep' (and clone: 'deep' for isolation).
- The mergeFrom symbol.
- How Neo.container.Base handles recursive injection.
Examples:
- Basic example: Injecting config into a direct child.
- Advanced example: Injecting config into a nested child (Structural Injection Pattern).
- Inheritance example: How subclasses override specific config objects without touching the structure.
Best Practices:
- Separating Structure (items) from Configuration (myConfig_).
- Using clone: 'deep' to prevent prototype pollution in shared container definitions.

Integration: Add the new guide to learn/tree.json under "Fundamentals & Core Concepts".

tobiu added the documentation label on Jan 12, 2026, 3:45 AM

tobiu added the enhancement label on Jan 12, 2026, 3:45 AM

tobiu added the ai label on Jan 12, 2026, 3:45 AM

tobiu referenced in commit e1ca4be - "docs: Add guide for Declarative Config Merging & Structural Injection (#8575)" on Jan 12, 2026, 3:48 AM

tobiu assigned to @tobiu on Jan 12, 2026, 3:48 AM

tobiu Jan 12, 2026, 3:48 AM

Input from Gemini 3 Pro:

✦ I have created the guide learn/guides/fundamentals/DeclarativeConfigMerging.md.

It covers:

The problem of "Configuration Drilling".

The solution using mergeFrom and Structural Injection.

Core concepts: isDescriptor, merge: 'deep', clone: 'deep'.

Code examples for implementation and subclassing.

Best practices for avoiding prototype pollution.

The guide is integrated into learn/tree.json.

Closing as completed.

tobiu referenced in commit 13eb383 - "docs: Explain Descriptor Merging in DeclarativeConfigMerging guide (#8575)" on Jan 12, 2026, 3:51 AM

tobiu Jan 12, 2026, 3:51 AM

Input from Gemini 3 Pro:

✦ I have updated the DeclarativeConfigMerging.md guide to include a section on Overriding Config Descriptors. This explains the mechanism behind the clone: 'deep' fix (where subclass descriptors now merge on top of parent descriptors) and provides context for the example usage.

Closing as completed.

tobiu closed this issue on Jan 12, 2026, 3:51 AM