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	15631
title	Scripted kinetic multi-window demo: popup drags across real OS windows
state	Closed
labels	enhancementdesignai
assignees	neo-kimi-iris
createdAt	Jul 21, 2026, 9:46 AM
updatedAt	Jul 21, 2026, 11:04 PM
githubUrl	https://github.com/neomjs/neo/issues/15631
author	neo-kimi-phoebe
commentsCount	5
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
contentTrust
projected
quarantined	0
signals	[]
blockedBy	[]
blocking	[]
closedAt	Jul 21, 2026, 11:04 PM

Scripted kinetic multi-window demo: popup drags across real OS windows

Closed Backlog/active-chunk-8 enhancementdesignai

neo-kimi-phoebe commented on Jul 21, 2026, 9:46 AM

Context

Operator direction (2026-07-21, Build Week submission window + standing demo boost): the current cut presents multi-window Neo statically — a detail panel already in a second window — while the engine's signature kinetic capability (animated drag of live panels across real OS windows, N popups, re-integration) is exactly what our e2e suite proves daily. The demo undersells the Body. Choreography v2: scripted popup drags performed deterministically, filmed, composited into the film's QT proof beat. Codex-weekly-reset gates only the dialogue TTS regeneration (Emmy's lane); visuals need nothing.

Live latest-open sweep: checked latest 20 open issues at 2026-07-21T07:35Z; no equivalent. A2A in-flight sweep: no competing claim (Emmy composites; Vega's #15624 is the anatomy leaf).

The Problem

A live component crossing an OS-window boundary mid-gesture — still subscribed, still updating, identity intact, then re-integrating — is the single most legible proof of Neo's multi-threaded object-permanence engine. Static two-window shots cannot show it. The film's QT beat and the standing demo both deserve the kinetic version.

The Architectural Reality

Everything needed is already shipped and proven:

FleetCockpit.popOutAgentDetail() + reattachAgentDetail() — click pop-out with reparent-never-recreate (detachedDetailPane re-adoption).
Gesture tear-out bookkeeping exists cockpit-side (the animated-drag path, separate from click pop-out).
operator-mailbox is a dock-pane item — the 2-popup bonus rides the same dock machinery (verify its pop-out path first).
Scripted gesture drive via InteractionService/Neural Link — the same path DemoBCrossWindowDragNL executes headed on this host.
macOS screencapture -v video capture proven by Emmy's capability probes.
#15629 (film-floor) merged: recapture materializes themes first (#15449 discipline).

The Fix

Verify the operator-mailbox pane's pop-out/tear-out path (10 min).
Author the deterministic shot list + scripted drive: drill into a resident → pop the detail out → animated drag into the right-side space → pop the mailbox out → drag it too → re-integrate the detail (the return proof).
Framing (operator constraint): only a LITTLE additional space right of the main window — ~4:1 ratio (main content stays dominant; the popup is the mover, not the stage). Ratio is explicitly challengeable at shot-list review.
Fallback: popup moved on top of the main viewport (single capture region) if desktop framing misbehaves.
Two identical takes via the scripted drive; keep the cleaner (determinism receipt). Stage restored after each take (the walkthrough contract).
Capture on this host (proven headed seat) with materialized themes; hand footage + timing map to Emmy for compositing.

Acceptance Criteria

Mailbox pane pop-out verified (or explicitly descoped with reason).
Scripted choreography executes identically twice (deterministic drive, no hand input).
Footage shows: 2 windows (detail), re-integration — live and updating throughout. The N windows (+mailbox) beat is explicitly descoped to follow-up #15650 by operator narrowing decision (2026-07-21, ratified in-session: the mailbox pop-out path is verified off-camera per AC1 receipts; its film beat rides the post-#15536-polish re-shoot and the gesture-executor question there).
4:1 main-to-side-space framing honored (or the challenge resolved with the operator).
Stage restored after each take (zero residue).
Footage + timing map delivered to Emmy for the QT beat.

Out of Scope

Dialogue TTS regeneration (Codex-reset gated — Emmy's lane; v3.1 script already with her).
Compositing/editing (Emmy).
Any new pop-out machinery (this is choreography on shipped seams, not a feature build — if a seam proves missing, file its own ticket).

D#15570 (the film) · PR #15479 (deterministic screenplay precedent) · #15629 (merged film-floor) · DemoBCrossWindowDragNL (scripted-drive precedent) · #15449 (theme materialization)

Origin Session ID: 3fe94880-447f-437e-b67f-1c063c12bc97

Retrieval Hint: kinetic multi-window demo popup drag popOutAgentDetail operator-mailbox scripted choreography QT proof beat 4:1