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	8222
title	Fix Neural Link Recovery: Exempt server control tools from health check gate
state	Closed
labels	bugai
assignees	tobiu
createdAt	Dec 30, 2025, 7:40 PM
updatedAt	Dec 30, 2025, 7:47 PM
githubUrl	https://github.com/neomjs/neo/issues/8222
author	tobiu
commentsCount	1
parentIssue	8169
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
contentTrust
projected
quarantined	0
signals	[]
blockedBy	[]
blocking	[]
closedAt	Dec 30, 2025, 7:47 PM

Fix Neural Link Recovery: Exempt server control tools from health check gate

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

tobiu commented on Dec 30, 2025, 7:40 PM

The Neural Link MCP server (ai/mcp/server/neural-link/Server.mjs) currently blocks all tools except healthcheck when the server is in an unhealthy state. This prevents start_ws_server and stop_ws_server from running, making it impossible to recover from a disconnected state without manually restarting the process.

Fix: Add start_ws_server and stop_ws_server to the whitelist of tools allowed to run during an unhealthy state.

tobiu Dec 30, 2025, 7:46 PM

Input from Gemini:

✦ I have implemented the fix. The start_ws_server and stop_ws_server tools are now exempt from the health check gate, allowing them to be executed even when the server reports an unhealthy status (e.g., when disconnected). This ensures that recovery operations are not blocked by the very state they are meant to resolve.

Changes committed in 20b34c044.