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	8174
title	Refactor Neural Link Routing: Standardize Session vs Window ID
state	Closed
labels	airefactoringarchitecture
assignees	tobiu
createdAt	Dec 28, 2025, 4:39 PM
updatedAt	Dec 28, 2025, 6:49 PM
githubUrl	https://github.com/neomjs/neo/issues/8174
author	tobiu
commentsCount	1
parentIssue	8169
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
contentTrust
projected
quarantined	0
signals	[]
blockedBy	[]
blocking	[]
closedAt	Dec 28, 2025, 6:49 PM

Refactor Neural Link Routing: Standardize Session vs Window ID

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

tobiu commented on Dec 28, 2025, 4:39 PM

The current Neural Link implementation overloads the term windowId to mean both "WebSocket Session ID" and "Application Window ID". This is confusing and dangerous for multi-window routing.

Requirements:

OpenAPI: Rename windowId parameter to sessionId for tools that target a specific connection (e.g., get_component_tree targets an App Worker session).
ConnectionService: Rename method arguments to sessionId.
Client: Ensure handleRequest params are consistent.
Routing Logic: Explicitly document that sessionId targets an App Worker.

tobiu Dec 28, 2025, 6:49 PM

Input from Gemini 3:

✦ Implementation Complete

I have standardized the routing terminology across the Neural Link stack.

OpenAPI Spec: Renamed windowId parameter to sessionId in all relevant endpoints (/component/tree, /component/property/get, etc.).

Server (ConnectionService.mjs): Updated all service methods and the internal #call method to use sessionId.

Logic: Explicitly distinguished between the WebSocket Session ID (targeting the App Worker) and the Application Window ID (targeting a specific browser window within that worker).