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	8001
title	Implement App Worker MCP Server PoC (Neural Link)
state	Closed
labels	documentationenhancementairefactoring
assignees	tobiu
createdAt	Dec 3, 2025, 2:50 AM
updatedAt	Dec 3, 2025, 3:14 AM
githubUrl	https://github.com/neomjs/neo/issues/8001
author	tobiu
commentsCount	0
parentIssue	7960
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Dec 3, 2025, 3:14 AM

Implement App Worker MCP Server PoC (Neural Link)

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

Closed v11.16.0 documentationenhancementairefactoring

tobiu commented on Dec 3, 2025, 2:50 AM

A Proof of Concept (PoC) has been implemented to establish a bidirectional communication channel between Node.js agents and the Neo.mjs App Worker.

Current Implementation (PoC):

BridgeService: A WebSocket server (ai/mcp/server/app-worker/services/BridgeService.mjs) running on port 8081.
MCP Server: A basic MCP server (ai/mcp/server/app-worker/Server.mjs) exposing bridgeReady and bridgeEvaluate tools.
SDK: AppWorker_BridgeService exported in ai/services.mjs.
Verification: A test script ai/examples/test-app-worker.mjs was created.

Known Issues & Refactoring Requirements:

Namespace Convention: Neo.ai.mcp.server.app_worker uses underscores; should be app-worker to match folder structure and existing patterns (e.g., knowledge-base).
Example App: The PoC modified examples/button/base, which is incorrect. A dedicated example app (e.g., examples/ai/bridge) must be created for testing.
Dependencies: ws was added to devDependencies but should be managed more carefully (optional dependency).
Architecture: BridgeService spawning the WebSocket server directly in construct/start needs review. It should likely be a separate concern or class.
Tool Registration: Manual tool registration in Server.mjs should be replaced with Neo.ai.mcp.ToolService.

Next Steps:

Rename namespaces.
Create a dedicated test example.
Refactor Server.mjs to use ToolService.
Clean up dependencies.

tobiu added the documentation label on Dec 3, 2025, 2:50 AM

tobiu added the enhancement label on Dec 3, 2025, 2:50 AM

tobiu added the ai label on Dec 3, 2025, 2:50 AM

tobiu added the refactoring label on Dec 3, 2025, 2:50 AM

tobiu assigned to @tobiu on Dec 3, 2025, 2:52 AM

tobiu added parent issue #7960 on Dec 3, 2025, 2:56 AM

tobiu referenced in commit 6d78b50 - "Implement App Worker MCP Server PoC (Neural Link) #8001" on Dec 3, 2025, 3:07 AM

tobiu closed this issue on Dec 3, 2025, 3:14 AM