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.

Neo.mjs - Self-Evolving Software Organism

Frontmatter

title	fix(e2e): bind AgentOS Neural Link tests to page session (#14858)
author	neo-gpt
state	Open
createdAt	7:36 PM
updatedAt	7:36 PM
closedAt
mergedAt
branches	`dev` ← `codex/14858-agentos-nl-e2e-session-binding`
url	https://github.com/neomjs/neo/pull/14859
contentTrust
projected
quarantined	0
signals	[]

Open

neo-gpt commented on 7:36 PM

Resolves #14858

AgentOS Neural Link E2Es now identity-bind to the Playwright page's own App Worker session even when the shared bridge already contains an older same-name agentos session. The shared fixture unwraps remote reply envelopes from Neo.worker.App.getWorkerId(), the lifecycle spec uses the fixture SDK instead of raw app-name lookup, and WindowOps filters topology by appWorkerId.

Evidence: L3 (live Chrome + Neural Link E2E probe on an isolated dev server with a stale same-name bridge session present) -> L3 required (#14858 current-page binding and focused ordering ACs). No residuals.

Deltas from ticket

Shared fixture hardening was required: a direct browser probe showed AgentOS SharedWorker getWorkerId() returning {action:"reply", data:"<sessionId>"}. The old fixture discarded that non-string envelope and fell back to app-name lookup.
Validation used an isolated webpack dev server on :8095 because the existing local :8080 server was stale and served the pre-#14847 AgentOS shell. No tracked validation config was added.

Test Evidence

node --check test/playwright/fixtures.mjs
node --check test/playwright/e2e/agentos/FleetCockpitLifecycleNL.spec.mjs
node --check test/playwright/e2e/neural-link/WindowOps.spec.mjs
git diff --check
npm run agent-preflight -- --no-fix test/playwright/fixtures.mjs test/playwright/e2e/agentos/FleetCockpitLifecycleNL.spec.mjs test/playwright/e2e/neural-link/WindowOps.spec.mjs
Direct probe against http://localhost:8095/apps/agentos/index.html: getWorkerId().data matched the current page session while the bridge still contained an older agentos session.
./node_modules/.bin/playwright test -c test/playwright/playwright.config.e2e.14858.mjs test/playwright/e2e/agentos/Cockpit.spec.mjs test/playwright/e2e/agentos/FleetCockpitLifecycleNL.spec.mjs test/playwright/e2e/neural-link/WindowOps.spec.mjs --workers=1 passed 4/4. The temporary config changed only baseURL to the fresh :8095 server and disabled webServer; it was removed before commit.

Post-Merge Validation

Re-run the focused ordering with canonical test/playwright/playwright.config.e2e.mjs after ensuring :8080 is a fresh dev server, not a stale reused process.

Commits

69a2011252 - fix(e2e): bind AgentOS Neural Link tests to page session (#14858)

Authored by Euclid (GPT-5, Codex Desktop). Session 019f306e-3ffb-7980-984b-175a3c0072ac.