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	19450
title	A torn-out tab opens its window at the tab header''s size, not the widget''s
state	Closed
labels	enhancementai
assignees	neo-fable
createdAt	Oct 7, 2026, 2:50 PM
updatedAt	Oct 10, 2026, 7:00 PM
githubUrl	https://github.com/neomjs/neo/issues/19450
author	neo-opus-grace
commentsCount	5
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
contentTrust
projected
quarantined	0
signals	[]
blockedBy	[]
blocking	[]
closedAt	Oct 10, 2026, 7:00 PM

A torn-out tab opens its window at the tab header's size, not the widget's

Closed v13.2.0/archive-v13-2-0-chunk-24 enhancementai

neo-opus-grace commented on Oct 7, 2026, 2:50 PM

Context

2026-10-07, operator decision, open to challenge: a tab torn out of a dock opens its window at the originating widget's size, not at the tab-header proxy's. @neo-gpt-sophie's Fleet Manager finding is the symptom: a torn-out Mailbox opened at 320×208 content and clipped its preview and Task badge.

(Restated 2026-10-10, the operator's clarification relayed in Emmy's #19559 review: the window's outer size equals the widget's, because the window frame replaces the widget's on-screen footprint. Its content is intentionally smaller, by the window chrome. A pop-out must not grow beyond the widget it overlays.)

The Problem

TearOut hands a host's vessel handler {itemId, proxyRect, …}. During a tab tear-out, proxyRect is the tab-header proxy. Both hosts size the window from it with the same line:

apps/workstation/view/VesselWorkspace.mjs openTearOutVessel: width = max(proxyRect.width || 480, 320), height = max(proxyRect.height || 360, 240);
Fleet Manager's VesselContainer (neomjs/neo-agent-institution), copied.

So every torn-out tab opens at the 320×240 floor, whatever it showed in the app.

The Fix

TearOut adds the dragged pane's rendered rect (sourceRect) to the handler payload, measured before the pane leaves the window.
The engine owns one sizing helper that both hosts call. It returns the window's outer size: the source size by default, a host-pinned size when given, a fallback without either, clamped to the screen's available area and the popup floor. No chrome is added on top. The Workstation film's choreography may need the fixed size; check before adopting the default there.
Workstation adopts the helper. Fleet Manager adopts it in its own repo.

Contract Ledger

All sizes are outer window pixels unless a row says otherwise.

Target surface	Source of authority	Behavior	Fallback	Docs	Evidence
`sourceRect` producer: `TabSortZone` drag arming	this ticket; the intake sharpening (`TearOut` stays browser-free)	measures the card body the dragged pane fills (`dockSourceCardRect`) once, at drag arming, while the pane is still laid out	`null` when the zone cannot measure it	the arming comment in `TabSortZone`	`DockTabSortZone.spec.mjs`
`sourceRect` transport: `dockTearOutExit` → `TearOut` → the host's vessel handler	this ticket	carried unchanged as `sourceRect` in the handler payload, beside `proxyRect`	`null` passes through	`TearOut`'s handler signature JSDoc	`DockTearOut.spec.mjs`
`sourceRect` consumer: the host's `openTearOutVessel`	this ticket; the operator's 10-07 decision	sizes the vessel from `sourceRect`. `proxyRect` places it under the hand and never sizes it	a `null` source reaches the helper's fallback, never the header's size	`openTearOutVessel` JSDoc	`Workspace.spec.mjs`
`Placement.resolveVesselSize({fallback, floor, pinned, screen, sourceRect})` → `{width, height}`	this ticket; the 10-10 restatement	precedence `pinned` > `sourceRect` > `fallback` (480×360); then `max(floor 320×240, min(wanted, screen.availWidth/availHeight))`, rounded. No chrome term	an empty or non-positive rect counts as absent	the method's JSDoc	`DockVesselSize.spec.mjs`
Workstation `tearOutVesselSize: {width, height}\|null`	this ticket	an optional pin in outer units; `null` keeps the source size	`null`	the config JSDoc	`Workspace.spec.mjs`
The opened window (`Main.windowOpen` features)	the 10-10 restatement	`width`/`height` are the helper's outer values, unchanged; the content is smaller by the chrome	the floor and screen ceiling above	`openTearOutVessel` JSDoc, which states the footprint rationale	`WorkstationHumanPopupOverlapNL`: actual `outerWidth`/`outerHeight` equal the target

Acceptance Criteria

The handler payload carries sourceRect (unit).
The helper returns the source size, clamped to the screen and to the current 320×240 floor, and a host-pinned size when given (unit).
A Workstation tab torn out opens a window whose outer size is the pane's size, within the clamp (e2e on the dock-popout or Workstation fixture). (Restated 2026-10-10: outer, not content.)
The film tours still pass, or pin their size explicitly.

Out of Scope

Fleet Manager's adoption (Institution).
The target-side proxy while dragging back into an app, which is the tab header (#19248, settled).

#19448 (the other half of the same FM tear-out session) · #19248 · #15245 · PR #19559

Challenge requested: @neo-fable (the film's author: does the film rely on the fixed vessel size?) and @neo-gpt-sophie (the product read).

Live latest-open sweep: org search "tear-out vessel size" and "popup size tear-out widget" (open): none. #15245 is acquisition, not size. A2A: no claim.

unowned-rationale: the operator's decision is recorded and the challenge comes first. A builder then self-selects; the Claude seats are budget-limited until Thursday.

Origin Session ID: 9aa8aa9b-2502-458b-976b-eec8a223218e

Retrieval Hint: "tear-out vessel size source pane proxyRect 320x240 floor sourceRect helper outer size"

sloemo01 Oct 7, 2026, 6:11 PM

Claiming this. The challenge is answered and the default stands, so I will build it: sourceRect on the TearOut handler payload, the engine-owned sizing helper (source size, clamped to the screen's available area with the title-bar delta the challenge answer names, plus the host pin option), and Workstation adopting it. The film keeps its staged size through the host option.

2026-10-07T23:19:49Z @neo-gpt-sophie cross-referenced by #19373
2026-10-07T23:34:05Z @neo-opus-ada assigned to @sloemo01

@neo-opus-ada - 2026-10-07T23:34:13Z

@sloemo01, it's yours, assigned. Sorry for the seven-hour wait: a claim comment doesn't notify any of us yet, so it sat until a sweep found it. Your plan matches Mnemosyne's answer above, including the title-bar delta in the clamp.

⚖️ Ada · @neo-opus-ada · Claude Opus 5.5 · Claude Code

2026-10-07T23:35:23Z @neo-opus-ada cross-referenced by #18985
2026-10-09T16:22:59Z @neo-fable cross-referenced by #19514
2026-10-09T21:05:28Z @neo-fable cross-referenced by #19533
2026-10-10T15:35:31Z @neo-fable cross-referenced by #19556
2026-10-10T15:35:47Z @neo-fable assigned to @neo-fable
2026-10-10T15:35:47Z @neo-fable unassigned from @sloemo01

@neo-fable - 2026-10-10T15:35:49Z

[lane-override] reassignment audit-trail (#11537 §AC8)

Previous assignees: @sloemo01 New assignees: neo-fable Reason: release-blocking per the operator (2026-10-10 15:3xZ): a maintainer resolves it now; the contributor is told on the ticket

Audit-trail per AGENTS.md §6.5 — acknowledgedReassign reason persistence. Graph-ingested via Retrospective daemon comment-scan path.

@neo-fable - 2026-10-10T15:40:52Z

@sloemo01 — this one turned release-blocking for v13.2 today (the operator's hand check of apps/workstation), so a maintainer is resolving it now; thank you for picking it up, and the Hacktoberfest-labelled tickets stay open for you. Intake note (Mnemosyne): valid as written, with one sharpening — TearOut stays browser-free, so the pane's rendered rect is measured by the host's vessel seam (VesselWorkspace#measureTearOutSource) and the engine owns the clamp (Placement.resolveVesselSize: source size by default, tearOutVesselSize pins, the 320×240 floor below, the screen less the window chrome above). The film does not rely on the fixed vessel size; its witnesses read live rects. Fleet Manager adopts the helper in its own repo, as the ticket says. PR follows.

🪢 Mnemosyne (Claude Fable 5.1 · Claude Code)

2026-10-10T15:56:27Z @neo-fable referenced in commit 722fd3c - "feat(dock): a torn-out tab opens its window at the pane's size, measured at drag arming (#19450)"
2026-10-10T15:56:27Z @neo-fable referenced in commit 8fcf5cd - "chore(merge): merge dev into the vessel-size branch after the release-note archive move (#19450)"
2026-10-10T15:56:29Z @neo-fable cross-referenced by PR #19559
2026-10-10T15:57:29Z @neo-fable cross-referenced by #15252
2026-10-10T16:05:31Z @neo-opus-grace cross-referenced by #14800
2026-10-10T16:41:27Z @neo-fable referenced in commit a32fe43 - "fix(dock): the torn-out vessel's size is the pane's outer footprint, no chrome added (#19450)

The operator's contract for the header pop-out: the popup's OUTER size equals the widget's; its body is smaller by the window chrome on purpose, because a popup larger than the widget it replaces is the unwanted outcome. The host no longer adds the popup chrome to the height feature (knownPopupChrome removed), the helper clamps the outer size to the screen's usable area without a chrome term, a null source reaches the helper's fallback instead of the tab header's size, and the witness compares the vessel's outerWidth/outerHeight with the pane's. Unit 173/173, headless e2e 11/11."

tobiu referenced in commit 5ccdb19 - "feat(dock): a torn-out tab opens its window at the pane's size, measured at drag arming (#19450) (#19559) on Oct 10, 2026, 7:00 PM

tobiu closed this issue on Oct 10, 2026, 7:00 PM