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	13753
title	First-widget cockpit-host (S1, verified) — slice of #13445
state	Open
labels	enhancementairefactoringarchitecture
assignees	[]
createdAt	Jun 21, 2026, 12:42 PM
updatedAt	3:22 PM
githubUrl	https://github.com/neomjs/neo/issues/13753
author	neo-opus-vega
commentsCount	1
parentIssue	13445
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
contentTrust
projected
quarantined	0
signals	[]
blockedBy	[]
blocking	[]

First-widget cockpit-host (S1, verified) — slice of #13445

Open Backlog/active-chunk-2 enhancementairefactoringarchitecture

neo-opus-vega commented on Jun 21, 2026, 12:42 PM

Context

Slice of #13445 (relocate the first-widget EvidencePane subtree into a dashboard.Container host). #13445's hard core (S2 cross-window detach) is un-verifiable headless — it needs a trusted-pointer harness session. This slice delivers + verifies the S1 half now.

Scope (S1 — verified)

A new apps/agentos/view/FirstWidgetPanel.mjs composite hosts the first-widget subtree (bounded intake + evidence pane + the live-grid stage) inline in the main cockpit's dashboard.Container, instead of a separate child app. Minimal-ripple: the composite reuses the existing subtree classes + their insert-observer controller in place (imported from the childapp view/), so getReference resolves in-tree and the deterministic projection seam fires verbatim — no file-move churn, existing unit/e2e suites stay green.

Verified live (e2e against this branch's dev server): the panel + intake + evidence pane + widget-stage render, and the controller boots the first grid into the stage (the insert-observer projection fires App-Worker-locally in the relocated host). Assertion added to test/playwright/e2e/AgentOSCockpit.spec.mjs.

Out of scope (stays on parent #13445)

The physical file-move of the subtree out of the childapp into apps/agentos/view/ + reducing the childapp shell to bare (this slice reuses in place to keep the diff focused + the suites green).
S2 — the grid popping to its own window via openWidgetInPopup/onWindowConnect with the evidence pane staying in the shell; cross-window getReference survival. Un-verifiable headless (trusted-pointer drag) — needs a running harness.

Acceptance

First-widget work-area renders in the cockpit dashboard.Container (S1), e2e-verified on this branch.
(parent #13445) file-move + childapp-reduce + S2 cross-window.

Refs #13445. Authored by @neo-opus-vega.