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	8983
title	Fix Grid Scrollbar Position and DragScroll ID Mismatch
state	Closed
labels	bug
assignees	tobiu
createdAt	Feb 4, 2026, 1:20 PM
updatedAt	Feb 4, 2026, 1:54 PM
githubUrl	https://github.com/neomjs/neo/issues/8983
author	tobiu
commentsCount	2
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Feb 4, 2026, 1:54 PM

Fix Grid Scrollbar Position and DragScroll ID Mismatch

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

Closed v12.0.0 bug

tobiu commented on Feb 4, 2026, 1:20 PM

Problem:

Vertical Scrollbar moves horizontally: The vertical scrollbar scrolls with the content instead of staying pinned.
GridDragScroll Regression: Horizontal drag scrolling is broken because ScrollManager passes the Component ID (id) instead of the rendered DOM ID (id__wrapper) to the GridDragScroll addon.

Fix:

Revert to overflow-y: hidden: We changed resources/scss/src/grid/Container.scss from overflow-y: clip back to overflow-y: hidden on the inner .neo-grid-container.
- Rationale: clip forces the parent wrapper (which has overflow-x: auto) to handle the scrolling. Since the vertical scrollbar is an absolute child of that wrapper, it scrolls away with the content. hidden creates a new Block Formatting Context (BFC) / Scroll Container on the inner element, trapping the wide content inside. This means the inner element scrolls, while the wrapper (and the scrollbar pinned to it) stays static.
Focus Scroll Prevention: The reason we originally moved to clip was to prevent the browser from scrolling the grid body into view when focused (which sometimes pushed headers out). We solved this properly in src/grid/Body.mjs by passing {preventScroll: true} to the focus() method in onRowClick.

tobiu added the bug label on Feb 4, 2026, 1:20 PM

tobiu referenced in commit a92ab46 - "fix: Restore Grid Scrollbar position and diagonal scrolling (#8983)" on Feb 4, 2026, 1:53 PM

tobiu Feb 4, 2026, 1:53 PM

Input from Gemini 3 Pro:

✦ I have resolved this issue.

Changes:

Reverted SCSS: Changed resources/scss/src/grid/Container.scss back to overflow-y: hidden. This restores the correct scrolling behavior where the inner container scrolls while the wrapper (and the pinned scrollbar) remains static.

Fixed Focus Logic: Updated src/grid/Body.mjs to use this.focus(this.vdom.id, false, true) in onRowClick. The true argument enables preventScroll, ensuring that focusing a row doesn't trigger unwanted browser scrolling behavior, which was the original reason for trying overflow-y: clip.

Note on DragScroll: No changes were made to ScrollManager.mjs or GridDragScroll.mjs. The regression in drag scrolling was a side effect of the broken overflow behavior. Restoring the correct CSS fixed both issues.

I have pushed the changes to the feature branch.

tobiu assigned to @tobiu on Feb 4, 2026, 1:53 PM

tobiu closed this issue on Feb 4, 2026, 1:54 PM

tobiu Feb 4, 2026, 1:54 PM

relates to #8981