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	9612
title	Grid Multi-Body: Scrollbar Refactoring and Vertical Restoration
state	Closed
labels	enhancementaigrid
assignees	tobiu
createdAt	Mar 31, 2026, 4:25 PM
updatedAt	Mar 31, 2026, 4:52 PM
githubUrl	https://github.com/neomjs/neo/issues/9612
author	tobiu
commentsCount	1
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Mar 31, 2026, 4:52 PM

Grid Multi-Body: Scrollbar Refactoring and Vertical Restoration

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

Closedenhancementaigrid

tobiu commented on Mar 31, 2026, 4:25 PM

As part of the Multi-Body Epic (#9486), this task focuses on refining the scrollbar architecture.

Requirements:

Vertical Scrollbar Restoration:
- Reapply the .neo-grid-body-wrapper CSS class to the bodyWrapper.
- Constrain the bodyWrapper flex item (e.g., min-width: 0) to prevent it from growing intrinsically and hiding its native vertical scrollbar off-screen.
HorizontalScrollbar Refactoring:
- Rename HorizontalScroller.mjs to HorizontalScrollbar.mjs to align with the historical VerticalScrollbar.
- Remove duplicated inline static styles (overflow-x: auto, overflow-y: hidden) from the JS config and VDOM.
- Centralize these styles in a dedicated SCSS file for the component.

tobiu added the enhancement label on Mar 31, 2026, 4:25 PM

tobiu added the ai label on Mar 31, 2026, 4:25 PM

tobiu added the grid label on Mar 31, 2026, 4:25 PM

tobiu referenced in commit c5d758a - "feat: Grid Multi-Body architecture vertical scrollbar restoration and horizontal scrollbar styling (#9612)" on Mar 31, 2026, 4:51 PM

tobiu referenced in commit 13ddbd0 - "feat: Add GridHorizontalScrollSync addon for multi-body scroller architecture (#9612)" on Mar 31, 2026, 4:51 PM

tobiu assigned to @tobiu on Mar 31, 2026, 4:52 PM

tobiu Mar 31, 2026, 4:52 PM

Completed the restructuring for the decoupled horizontal scrollbar architecture:

Renamed HorizontalScroller to HorizontalScrollbar and relocated its inline styles to a dedicated SCSS file.
Created GridHorizontalScrollSync addon to synchronize horizontal scrolling between the GridContainer components.
Verified that horizontal scrolling causes both body and header columns to remain 1:1 synchronized perfectly.
Restored the native vertical scrollbar pinned firmly inside the bodyWrapper against the right edge (via min-width: 0).

Closing as this fully satisfies the scrollbar decoupling requirements of the Grid Multi-Body architecture.

tobiu closed this issue on Mar 31, 2026, 4:52 PM