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	8331
title	Enhance Neural Link Health Check Response
state	Closed
labels	enhancementaiarchitecture
assignees	tobiu
createdAt	Jan 5, 2026, 12:51 PM
updatedAt	Jan 5, 2026, 1:16 PM
githubUrl	https://github.com/neomjs/neo/issues/8331
author	tobiu
commentsCount	0
parentIssue	8169
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
contentTrust
projected
quarantined	0
signals	[]
blockedBy	[]
blocking	[]
closedAt	Jan 5, 2026, 1:16 PM

Enhance Neural Link Health Check Response

Closed v11.18.0/archive-v11-18-0-chunk-2 enhancementaiarchitecture

tobiu commented on Jan 5, 2026, 12:51 PM

The current healthcheck response contains a redundant details array and lacks specific identification for active sessions and windows.

Goal:

Remove the details array.
Enrich the response object to include:
- sessions: List of active App Worker Sessions (id, connectedAt).
- windows: List of connected Windows (id, appName, width, height, x, y).
- agents: List of other connected Agents (ids).

Rationale for Dimensions: Including basic dimensions (width/height) helps immediately distinguish between main application windows and smaller popups/dialogs without requiring an extra get_window_topology call, saving agent turns.

Changes:

ConnectionService.getStatus(): Return richer window metadata.
HealthService.healthcheck(): Construct the new response payload.
openapi.yaml: Update HealthCheckResponse schema.

Reference: #8169 (Epic)

tobiu added the enhancement label on Jan 5, 2026, 12:51 PM

tobiu added the ai label on Jan 5, 2026, 12:51 PM

tobiu added the architecture label on Jan 5, 2026, 12:51 PM

tobiu assigned to @tobiu on Jan 5, 2026, 12:51 PM

tobiu added parent issue #8169 on Jan 5, 2026, 12:51 PM

tobiu referenced in commit 9613d44 - "feat(ai): Enhance Neural Link health check response (#8331) on Jan 5, 2026, 12:56 PM

tobiu closed this issue on Jan 5, 2026, 1:16 PM