What is the Neural Link?

The Neural Link is a bi-directional bridge that connects AI agents directly to the Neo.mjs runtime. It lets agents inspect the Scene Graph, component state, event listeners, computed styles, and DOM rectangles, and mutate the running application in real time.

Why is Neo.mjs called an Application Engine instead of a framework?

Neo.mjs maintains persistent application objects in a worker-backed Scene Graph instead of compiling application state away into ephemeral DOM nodes. That architecture enables multi-window orchestration, runtime permutation, and deep AI introspection.

What is Context Engineering?

Context Engineering shapes the information and tool environment around AI agents. Neo.mjs implements it through Knowledge Base, Memory Core, GitHub Workflow, and Neural Link MCP servers for frontier harnesses, plus a File System MCP server for internal Neo.ai.Agent local loops.

What is the Neo.mjs Agent OS?

The Neo.mjs Agent OS is the repository Brain: source code and services for Memory Core, Knowledge Base, Active Hybrid GraphRAG, DreamService, Golden Path synthesis, A2A coordination, and Neural Link tooling.

Frontmatter

id	8136
title	Create guide: Worker Architecture & Messaging
state	Closed
labels	documentationenhancementai
assignees	tobiu
createdAt	Dec 17, 2025, 3:57 AM
updatedAt	Dec 17, 2025, 5:31 AM
githubUrl	https://github.com/neomjs/neo/issues/8136
author	tobiu
commentsCount	0
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
contentTrust
projected
quarantined	0
signals	[]
blockedBy	[]
blocking	[]
closedAt	Dec 17, 2025, 5:31 AM

Create guide: Worker Architecture & Messaging

Closed v11.17.0/archive-v11-17-0-chunk-1 documentationenhancementai

tobiu commented on Dec 17, 2025, 3:57 AM

Create a new comprehensive guide learn/guides/fundamentals/WorkerArchitecture.md that explains the multi-threaded architecture of Neo.mjs.

Scope:

Worker Model: Explain the distinct roles of App, VDom, Data, and Main threads.
Message Routing: Detail how Neo.worker.Manager and Neo.worker.Base orchestrate communication.
Communication Patterns:
- Standard (RPC): App -> Main -> App (e.g., Addons).
- Triangular (VDOM): App -> VDom -> Main -> App (Optimization for DOM updates).
- Direct (MessageChannel): App <-> Canvas (Peer-to-peer optimization).
Remote Method Access (RMA): Explain the "magic" behind the proxy methods, promises, and error handling across threads.
Use Cases: Provide examples of when each pattern is used and why.

Update learn/tree.json: Add the new guide entry to the guides/fundamentals section.

tobiu added the documentation label on Dec 17, 2025, 3:57 AM

tobiu added the enhancement label on Dec 17, 2025, 3:57 AM

tobiu added the ai label on Dec 17, 2025, 3:57 AM

tobiu assigned to @tobiu on Dec 17, 2025, 3:57 AM

tobiu referenced in commit 3c43954 - "Create guide: Worker Architecture & Messaging (#8136)" on Dec 17, 2025, 5:29 AM

tobiu closed this issue on Dec 17, 2025, 5:31 AM