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	14855
title	E2E: Neural Link WindowOps cannot discover the AgentOS dashboard host
state	Open
labels	bugaitestingregression
assignees	[]
createdAt	5:35 PM
updatedAt	5:35 PM
githubUrl	https://github.com/neomjs/neo/issues/14855
author	neo-gpt
commentsCount	0
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
contentTrust
projected
quarantined	0
signals	[]
blockedBy	[]
blocking	[]

E2E: Neural Link WindowOps cannot discover the AgentOS dashboard host

Open Backlog/active-chunk-4 bugaitestingregression

neo-gpt commented on 5:35 PM

Problem

The Neural Link WindowOps E2E fails before it can validate popup focus/position behavior because the AgentOS dashboard host is no longer discoverable through the expected Neural Link component query. This leaves the multi-window popup operation path without a passing end-to-end proof.

Evidence

Verified on dev at merge commit ecbb21cde9a72f40f7a6c7132baedecd25db6bdd after PR #14849 merged.

Command run:

./node_modules/.bin/playwright test -c tmp/e2e-full-8097.config.mjs

The temporary config matched the E2E config but used http://localhost:8097 with reuseExistingServer: false, because port 8080 was already occupied by another Neo checkout.

Suite result: 73 tests run, 56 passed, 17 failed.

Failure:

test/playwright/e2e/neural-link/WindowOps.spec.mjs:24: dashboard host should be discoverable through Neural Link; expected queried panel count > 0, received 0 for AgentOS.view.FleetSettingsPanel.

Nearby controls that passed in the same run include neural-link/ChildappConnect.spec.mjs, CreateComponent.spec.mjs, CreateComponentMultiWindow.spec.mjs, CreateGrid.spec.mjs, RemoveComponent.spec.mjs, TransactionArchiveReplay.spec.mjs, and the WriteGuard live E2E specs. That points to the WindowOps host/query contract rather than a global Neural Link bridge outage.

Acceptance Criteria

WindowOps.spec.mjs discovers the intended AgentOS dashboard/panel host through the current source-of-authority selector, or the test is updated to the renamed/restructured component with rationale.
Popup open/focus/position calls execute after host discovery and pass against the live multi-window topology.
Focused rerun passes:

./node_modules/.bin/playwright test -c test/playwright/playwright.config.e2e.mjs test/playwright/e2e/neural-link/WindowOps.spec.mjs

Duplicate Sweep

Latest 30 open issues checked: no matching open ticket.
Targeted GitHub search checked: WindowOps dashboard host discoverable Neural Link returned no open issues.
Local synced issue/discussion cache checked for WindowOps; hits referenced prior tickets that used this spec as evidence, not an open active duplicate for the current failure.