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	8215
title	Expose connected agents in Neural Link health check
state	Closed
labels	enhancementai
assignees	tobiu
createdAt	Dec 30, 2025, 11:24 AM
updatedAt	Dec 30, 2025, 11:30 AM
githubUrl	https://github.com/neomjs/neo/issues/8215
author	tobiu
commentsCount	0
parentIssue	8169
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
contentTrust
projected
quarantined	0
signals	[]
blockedBy	[]
blocking	[]
closedAt	Dec 30, 2025, 11:30 AM

Expose connected agents in Neural Link health check

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

tobiu commented on Dec 30, 2025, 11:24 AM

The Neural Link Bridge knows which agents are connected. This information should be exposed in the health check response to allow agents to see if they are "alone" or if other agents are present.

Tasks:

Bridge Update: Modify Bridge.mjs to broadcast agent_connected and agent_disconnected events to all connected agents (similar to how it handles apps).
Client Update: Update ConnectionService.mjs to listen for these events and maintain a local agents registry.
Schema Update: Update openapi.yaml to include an agents array in the HealthCheckResponse schema.
Service Update: Update HealthService.mjs to expose this data.

This provides better observability into the multi-agent environment.