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	7960
title	Spike: Bidirectional RMA Proof of Concept
state	Closed
labels	enhancementaiarchitecture
assignees	tobiu
createdAt	Nov 30, 2025, 10:58 PM
updatedAt	Dec 4, 2025, 4:45 AM
githubUrl	https://github.com/neomjs/neo/issues/7960
author	tobiu
commentsCount	1
parentIssue	null
subIssues	8001 Implement App Worker MCP Server PoC (Neural Link) 8002 Refactor App Worker MCP Server to use ToolService 8003 Make AI Tooling Dependencies Optional 8004 Create Dedicated Example App for AI Bridge Testing 8007 Implement Dynamic Loading for NeuralLink 8010 Align Neural Link MCP Server with Memory Core Server 8008 Create Neural Link Testbed App 8013 Implement End-to-End Tests for Neural Link 8006 Implement Neo.ai.NeuralLink (App Worker) 8014 Update ai/services.mjs to use Neural Link
subIssuesCompleted	10
subIssuesTotal	10
blockedBy	[]
blocking	[]
closedAt	Dec 4, 2025, 4:45 AM

Spike: Bidirectional RMA Proof of Concept

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

Closed v11.16.0 enhancementaiarchitecture

tobiu commented on Nov 30, 2025, 10:58 PM

Goal: Validate core technical assumptions with a minimal working prototype.

Time-box: 2-3 days

Connection Model: Browser Connects to Agent Server (Agent runs WebSocket server).

Deliverables:

Minimal Neo.ai.server.WebSocket (50 lines).
Agent can call ONE browser method: createNeoInstance.
Browser can call ONE agent method: analyzeComponent.
Document unexpected challenges.

Validation Checklist:

Message Ordering: Verify RPC call -> response correlation.
Lifecycle: Connection survives browser tab backgrounding.
Payloads: Can handle large payloads (>1MB).
Latency: Measure round-trip time under load.
Error Propagation: Agent exception -> Browser catch block (and vice-versa).
Multi-window Routing: Can target specific windowId.

Success Criteria:

Demonstrates bidirectional RPC works.
Measures baseline latency.
Identifies hidden complexity.

Non-Goals:

Security (hardcoded capabilities).
Production quality (prototype code).

Blockers:

Need to understand Neo's existing WebSocket RMA internals.

Reference: .github/AGENT_ARCHITECTURE.md

tobiu added the enhancement label on Nov 30, 2025, 10:58 PM

tobiu added the ai label on Nov 30, 2025, 10:58 PM

tobiu added the architecture label on Nov 30, 2025, 10:58 PM

tobiu cross-referenced by #7961 on Dec 1, 2025, 11:57 AM

tobiu added sub-issue #8001 on Dec 3, 2025, 2:56 AM

tobiu added sub-issue #8002 on Dec 3, 2025, 2:56 AM

tobiu added sub-issue #8003 on Dec 3, 2025, 2:56 AM

tobiu added sub-issue #8004 on Dec 3, 2025, 2:56 AM

tobiu cross-referenced by #8006 on Dec 3, 2025, 10:56 AM

tobiu cross-referenced by #8007 on Dec 3, 2025, 10:56 AM

tobiu cross-referenced by #8008 on Dec 3, 2025, 10:56 AM

tobiu added sub-issue #8007 on Dec 3, 2025, 2:43 PM

tobiu added sub-issue #8010 on Dec 3, 2025, 3:06 PM

tobiu added sub-issue #8008 on Dec 3, 2025, 3:07 PM

tobiu assigned to @tobiu on Dec 3, 2025, 10:38 PM

tobiu added sub-issue #8013 on Dec 3, 2025, 10:40 PM

tobiu added sub-issue #8006 on Dec 3, 2025, 10:50 PM

tobiu added sub-issue #8014 on Dec 3, 2025, 11:12 PM

tobiu Dec 4, 2025, 4:45 AM

resolved

tobiu closed this issue on Dec 4, 2025, 4:45 AM