What is the 'Neural Link'?

The Neural Link is a bi-directional bridge that connects AI agents (like Gemini or Claude) directly to the Neo.mjs runtime. It allows agents to 'see' the application's Scene Graph, inspect component state, verify event listeners, and even mutate the running application in real-time. This turns the application into a 'glass box' for AI, enabling autonomous debugging and feature development.

Why is Neo.mjs called an 'Application Engine' instead of a framework?

Traditional frameworks are general-purpose libraries (like a Toyota) that help you organize code, but they compile away into ephemeral DOM nodes. Neo.mjs is a precision-engineered runtime (like an F1 car), similar to Unreal Engine for games. It maintains a persistent 'Scene Graph' of objects in a separate worker thread. These objects retain their identity, state, and relationships, allowing for advanced capabilities like multi-window orchestration, runtime permutation, and deep AI introspection that are impossible with 'melted plastic' DOM-based frameworks.

What is 'Context Engineering'?

Context Engineering is the practice of curating the environment and information flow for AI agents to maximize their autonomy. In Neo.mjs, this is implemented via three Model Context Protocol (MCP) servers: a Knowledge Base for semantic code understanding, a Memory Core for learning from past sessions, and a GitHub Workflow server for project management. This ecosystem allows agents to work as fully integrated members of the development team.

What is 'Object Permanence' in the context of Neo.mjs?

In Neo.mjs, UI components are persistent JavaScript objects living in the App Worker, not just transient rendering results. This 'Object Permanence' means a component (like a Dashboard) maintains its state (scroll position, user input, internal logic) even if it is detached from the DOM or moved to a different browser window. This is the 'Lego Technic' approach versus the 'Duplo' approach of traditional frameworks.

What is an 'Agent Operating System'?

Neo.mjs v11 introduced the concept of an Agent OS, where the platform itself provides the tools and interfaces for AI agents to operate. It combines a standalone, type-safe AI SDK for autonomous 'Code Execution' with the Neural Link for runtime control. This enables agents to monitor, debug, and heal the application autonomously, effectively acting as an operating system for synthetic intelligence.

How does Neo.mjs handle multi-window applications?

Neo.mjs uses shared web workers to run a single application instance across multiple browser windows. All windows share the same application state and data in real-time. Components can even move between windows while retaining their JavaScript instances. This enables desktop-class experiences like multi-window IDEs, browser-based email clients, and multi-screen control rooms.

What makes Neo.mjs different from React, Angular, or Vue?

Neo.mjs is fundamentally different in its architecture: (1) It uses True Multithreading via web workers to prevent UI jank, (2) It is an AI-Native Application Engine with built-in bridges for AI collaboration, and (3) It treats components as persistent objects in a Scene Graph, enabling native multi-window support and runtime permutation.

Frontmatter

id	9633
title	Grid: Rename bodyWrapper to view
state	Closed
labels	enhancementairefactoringarchitecturegrid
assignees	tobiu
createdAt	Apr 2, 2026, 3:06 PM
updatedAt	Apr 2, 2026, 3:49 PM
githubUrl	https://github.com/neomjs/neo/issues/9633
author	tobiu
commentsCount	1
parentIssue	9626
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Apr 2, 2026, 3:49 PM

Grid: Rename bodyWrapper to view

Name: Neo.mjs Application Engine
Author: Neo.mjs

Closedenhancementairefactoringarchitecturegrid

tobiu commented on Apr 2, 2026, 3:06 PM

Description

In Epic #9626, we redesigned the Multi-Body Grid to use a unified vertical scroll mechanism and centralized VDOM orchestration under a new class: neo.grid.View.

However, throughout the framework (grid.Container, ScrollManager.mjs, Grid Addons, and SCSS), the config parameter holding this component, its instance-id attributes, and its DOM class are still named bodyWrapper / .neo-grid-body-wrapper.

Calling it bodyWrapper only describes its structural position in the DOM. Using view correctly reflects its new architectural role as the native viewport and VDOM orchestrator.

Objective

Rename bodyWrapper to view across the repository to lock in the new Multi-Body architecture vocabulary.

Required refactoring targets:

Config/Properties: bodyWrapper -> view in grid.Container.
Addon Variables: bodyWrapperId -> viewId (used in GridRowScrollPinning, GridHorizontalScrollSync, GridRowHoverSync, and ScrollManager).
SCSS/DOM: The .neo-grid-body-wrapper CSS class should become .neo-grid-view.
Testing: Update Playwright E2E tests utilizing these selectors.

Context

This is a follow-up sub-issue to Epic #9626 to finalize the architectural naming convention.

tobiu added the enhancement label on Apr 2, 2026, 3:06 PM

tobiu added the ai label on Apr 2, 2026, 3:06 PM

tobiu added the refactoring label on Apr 2, 2026, 3:06 PM

tobiu added the architecture label on Apr 2, 2026, 3:06 PM

tobiu added the grid label on Apr 2, 2026, 3:06 PM

tobiu added parent issue #9626 on Apr 2, 2026, 3:06 PM

tobiu referenced in commit 3b0d468 - "feat: multi-body grid flattened DOM architecture (#9633)" on Apr 2, 2026, 3:48 PM

tobiu Apr 2, 2026, 3:49 PM

Input from Gemini 3.1 Pro (Antigravity):

✦ The full architectural shift towards a flattened DOM structure for the multi-body grid is now complete. The legacy .neo-grid-body-wrapper nodes have been removed, CSS coordinates updated, and all scrolling interactions (including pointer dragging, native scroll, hover sync, horizontal sync, drag scroll) have been adapted mapping correctly to the single <div class="neo-grid-view"> container.

Key Sync Restoration: We successfully restored the VDOM meta-payload update mechanism for GridRowScrollPinning. getVdomUpdateMeta was relocated from the now-independent Grid Bodies directly to the Grid.View, effectively transporting the optical pinning scrollTop baseline accurately through purely automated DeltaUpdate payloads aligned with Main thread rendering frames.

I have committed and pushed the changes to the dev branch. Remaining test telemetry optimization is out of scope and explicitly deferred.

tobiu assigned to @tobiu on Apr 2, 2026, 3:49 PM

tobiu closed this issue on Apr 2, 2026, 3:49 PM