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	19625
title	The dashboard post''s step 5 lists WindowPosition, which the dock will load itself
state	Closed
labels	documentationenhancementBlog Postai
assignees	neo-opus-ada
createdAt	Oct 11, 2026, 9:25 PM
updatedAt	Oct 12, 2026, 2:12 PM
githubUrl	https://github.com/neomjs/neo/issues/19625
author	neo-opus-ada
commentsCount	0
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
contentTrust
projected
quarantined	0
signals	[]
blockedBy	[x] 19619 A tear-out Workspace without the WindowPosition addon fails silently
blocking	[]
closedAt	Oct 11, 2026, 9:51 PM

The dashboard post's step 5 lists WindowPosition, which the dock will load itself

Closed v13.2.0/archive-v13-2-0-chunk-25 documentationenhancementBlog Postai

neo-opus-ada commented on Oct 11, 2026, 9:25 PM

Context

learn/blog/building-a-multi-window-dashboard-with-dock-layouts.md (#19614, merged as ca3b95460f) tells the reader to add WindowPosition, beside DockFlip, to mainThreadAddons. On dev that advice is correct: without the addon, a window dragged by its title bar paints no drop zones over another (Grace's 18:43Z FM diagnosis).

#19622 (resolves #19619, cut-blocking) changes it. The dock then loads WindowPosition into each window it arms (getAddon per window, the host gated on Neo.currentWorker.isSharedWorker). Once that merges, listing the addon is harmless but no longer needed, and the post would teach a step the engine already does.

The Fix

After #19622 merges, re-read step 5 against its final code:

Drop WindowPosition from the shown config, and say the dock loads it per window.
Keep DockFlip unless the same change covers it.

The same re-read applies to stage 1 (multi-window-dashboards-with-dock-layouts.md) only if it names the addon; at ca3b95460f it doesn't.

Acceptance Criteria

Step 5's config and prose match Workspace.mjs after #19622: no step the engine already performs.
The edit lands before the 13.2 cut if #19622 does, so the post and the engine ship in the same package.

Out of Scope

The engine change itself (#19619).

#19614, #19618, #19619, #19622

Live latest-open sweep: no equivalent at 2026-10-11T19:2xZ.

tobiu closed this issue on Oct 11, 2026, 9:51 PM

tobiu referenced in commit 309f268 - "docs(blog): step 5 leaves WindowPosition to the dock, which loads it per window (#19625) (#19628) on Oct 11, 2026, 9:51 PM