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	8960
title	Fix: Vertical scrolling causes OffscreenCanvas loss in Grid cells
state	Closed
labels	bugai
assignees	tobiu
createdAt	Feb 3, 2026, 1:36 PM
updatedAt	Feb 3, 2026, 1:43 PM
githubUrl	https://github.com/neomjs/neo/issues/8960
author	tobiu
commentsCount	1
parentIssue	8930
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Feb 3, 2026, 1:43 PM

Fix: Vertical scrolling causes OffscreenCanvas loss in Grid cells

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

Closed v12.0.0 bugai

tobiu commented on Feb 3, 2026, 1:36 PM

We are observing a glitch where vertically scrolling the grid can cause some OffscreenCanvas instances (like Sparklines) to be "lost" or appear blank.

Analysis: This likely relates to the buffered row range mechanism in Neo.grid.Body. When rows are recycled or moved, the VDOM diffing engine might be generating move operations or destructive updates that interfere with the OffscreenCanvas persistence, similar to the horizontal scrolling issue but on the vertical axis.

Investigation Plan:

Inspect src/grid/Body.mjs and its row recycling/buffering logic.
Analyze VDOM deltas during vertical scrolling to identify if DOM nodes are being destroyed/recreated instead of moved/updated.
Ensure that canvas elements within the recycled rows maintain their worker association.

Goal: Ensure OffscreenCanvas instances remain stable and connected to their workers during vertical scrolling and row recycling.

tobiu added the bug label on Feb 3, 2026, 1:36 PM

tobiu added the ai label on Feb 3, 2026, 1:36 PM

tobiu referenced in commit 71ba8ff - "Fix: Vertical scrolling causes OffscreenCanvas loss in Grid cells (#8960)" on Feb 3, 2026, 1:43 PM

tobiu added parent issue #8930 on Feb 3, 2026, 1:43 PM

tobiu Feb 3, 2026, 1:43 PM

Input from Gemini 3 Pro:

✦ I have implemented the fix for the vertical scrolling glitch where OffscreenCanvas instances were being lost.

Root Cause: The mountedRows logic in src/grid/Body.mjs was calculating the render window based strictly on visible + buffer. At the boundaries of the dataset (top and bottom), this window size was smaller than the Recycle Modulus (available rows + 2 * buffer). Because the number of rendered rows fluctuated (e.g., shrinking to 15 at the top vs 20 in the middle), the VDOM engine interpreted the re-appearance of the "spare" rows as new insertions (insertNode), which destroys the DOM node and the associated Worker connection.

Fix Implemented: Modified updateMountedAndVisibleRows to enforce a Constant Window Size equal to the Recycle Modulus.

At the top of the grid, the window is "pushed down" to include look-ahead rows, filling the recycle pool.

At the bottom, the window is "pulled up" to include look-behind rows.

Outcome: The set of Row IDs {row-0 ... row-N} now remains constant as long as the dataset is large enough. This ensures the VDOM engine always generates moveNode operations for row recycling, preserving the OffscreenCanvas contexts and eliminating the visual glitch during vertical scrolling.

tobiu assigned to @tobiu on Feb 3, 2026, 1:43 PM

tobiu closed this issue on Feb 3, 2026, 1:43 PM