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	8182
title	Feat: Neural Link Identity and Recovery
state	Closed
labels	enhancementai
assignees	tobiu
createdAt	Dec 28, 2025, 8:37 PM
updatedAt	Dec 28, 2025, 8:48 PM
githubUrl	https://github.com/neomjs/neo/issues/8182
author	tobiu
commentsCount	1
parentIssue	8169
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
contentTrust
projected
quarantined	0
signals	[]
blockedBy	[]
blocking	[]
closedAt	Dec 28, 2025, 8:48 PM

Feat: Neural Link Identity and Recovery

Closed v11.18.0/archive-v11-18-0-chunk-1 enhancementai

tobiu commented on Dec 28, 2025, 8:37 PM

Enhance Neural Link connection logic to support session recovery via a persistent appWorkerId.

Client-Side (src/ai/Client.mjs):

Append ?appWorkerId=${Neo.worker.App.id} to the WebSocket URL.
This allows the server to identify the connection immediately.

Server-Side (ai/mcp/server/neural-link/services/ConnectionService.mjs):

Parse the appWorkerId from the request URL in handleConnection.
Use appWorkerId as the primary key for the session map (or map it to the sessionId).
If a connection with the same appWorkerId exists, disconnect the old one and replace it with the new one (handling reconnection).
Update call() logic to wait/retry if the session is temporarily offline but has a known appWorkerId.

Goal: Ensure the MCP server can recover from network blips or client reloads without losing the logical session identity.

tobiu Dec 28, 2025, 8:48 PM

Input from Gemini 3.0:

✦ I have implemented the resilience and identity enhancements.

Key Changes:

Persistent Identity: Neo.ai.Client now appends ?appWorkerId=... to the WebSocket connection URL.

Session Mapping: ConnectionService uses this appWorkerId as the stable sessionId key. This allows the server to recognize re-connections from the same application instance.

Call Recovery: ConnectionService.call() now gracefully handles missing sessions by entering a waitForSession state.

Auto-Start: If the server is not running when a call is attempted, it automatically starts, allowing for recovery from server crashes or stops.

The Neural Link is now robust against network interruptions and server restarts.