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	7958
title	Epic: Telemetry & Observability
state	Closed
labels	epicstaleaiarchitecture
assignees	[]
createdAt	Nov 30, 2025, 10:51 PM
updatedAt	Oct 9, 2026, 6:12 PM
githubUrl	https://github.com/neomjs/neo/issues/7958
author	tobiu
commentsCount	3
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
contentTrust
projected
quarantined	0
signals	[]
blockedBy	[]
blocking	[]
closedAt	Mar 15, 2026, 5:08 AM

Epic: Telemetry & Observability

Closed v12.1.0/archive-v12-1-0-chunk-1 epicstaleaiarchitecture

tobiu commented on Nov 30, 2025, 10:51 PM

Implement the "Hybrid Client" and Event Streaming logic to solve the "Blind Agent" problem.

Scope:

Agent Event Listener: Update Neo.ai.Agent to support simultaneous MCP (Tool) and WebSocket (Event) connections.
Worker-side Log Interceptor: Create Neo.worker.mixin.LogBridge to capture console logs and exceptions in App/Data/Canvas workers.
Log Forwarding: Stream these logs via the WebSocket RMA channel to the Agent.
Event Stream: Expose high-level Neo.mjs framework events (neo:window:connect, neo:component:mount) to the Agent.
Event Filtering: Implement subscription mechanism (e.g., agent.subscribe(['neo:error'])) to prevent flooding.

Strategic Goal: Enable agents to "see" runtime errors and state changes immediately without polling.

Reference: .github/AGENT_ARCHITECTURE.md

tobiu added the epic label on Nov 30, 2025, 10:51 PM

tobiu added the ai label on Nov 30, 2025, 10:51 PM

tobiu added the architecture label on Nov 30, 2025, 10:51 PM

tobiu cross-referenced by #7961 on Dec 1, 2025, 11:57 AM