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	8212
title	Enhance Neural Link Health Check with detailed diagnostics
state	Closed
labels	enhancementai
assignees	tobiu
createdAt	Dec 30, 2025, 10:46 AM
updatedAt	Dec 30, 2025, 11:13 AM
githubUrl	https://github.com/neomjs/neo/issues/8212
author	tobiu
commentsCount	1
parentIssue	8169
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
contentTrust
projected
quarantined	0
signals	[]
blockedBy	[]
blocking	[]
closedAt	Dec 30, 2025, 11:13 AM

Enhance Neural Link Health Check with detailed diagnostics

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

tobiu commented on Dec 30, 2025, 10:46 AM

The current HealthService for neural-link provides a basic status. To improve diagnostics and align with the memory-core implementation, we need to enhance the health check response.

Goal: Update ai/mcp/server/neural-link/services/HealthService.mjs to return a more detailed health payload, including:

Bridge Connection: Status of the connection to the standalone Bridge process.
Bridge Process: Status of the Bridge process (if managed/spawned by the service).
Session Details: More granular info about connected Agents and Apps.
Startup Status: Information about the initialization sequence.

Tasks:

Enhance HealthService.mjs to return the enriched payload.
Update openapi.yaml (HealthCheckResponse schema) to match the new structure.
Ensure backward compatibility or clear error messaging for clients expecting the old format (though internal agents adapt quickly).

Reference: See ai/mcp/server/memory-core/services/HealthService.mjs for the target pattern.

tobiu Dec 30, 2025, 10:47 AM

Input from Gemini:

✦ I have enhanced the HealthService and openapi.yaml to provide detailed diagnostics. The healthcheck tool now returns information about:

Bridge Connection: Whether the agent is connected to the Bridge process.

Session Stats: Number of active apps and windows.

Agent Identity: The unique Agent ID used for routing.

This completes ticket #8212.

tobiu cross-referenced by #8214 on Dec 30, 2025, 11:19 AM