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	9186
title	Fix Scroll Thrashing during Store Streaming
state	Closed
labels	bugdeveloper-experienceai
assignees	tobiu
createdAt	Feb 16, 2026, 2:19 PM
updatedAt	Feb 16, 2026, 2:32 PM
githubUrl	https://github.com/neomjs/neo/issues/9186
author	tobiu
commentsCount	1
parentIssue	9106
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Feb 16, 2026, 2:31 PM

Fix Scroll Thrashing during Store Streaming

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

Closed v12.0.0 bugdeveloper-experienceai

tobiu commented on Feb 16, 2026, 2:19 PM

Streaming data via StreamProxy currently causes the Grid to reset its scroll position to the top on every chunk load. This happens because Store.onCollectionMutate fires load events without the postChunkLoad flag, causing GridBody to treat each chunk as a new dataset.

Fix: Update src/data/Store.mjs to include postChunkLoad: !!me.isStreaming in the load event payload triggered by onCollectionMutate. This allows the Grid to maintain the user's scroll position while data streams in.

tobiu added the bug label on Feb 16, 2026, 2:19 PM

tobiu added the developer-experience label on Feb 16, 2026, 2:19 PM

tobiu added the ai label on Feb 16, 2026, 2:19 PM

tobiu added parent issue #9106 on Feb 16, 2026, 2:19 PM

tobiu assigned to @tobiu on Feb 16, 2026, 2:20 PM

tobiu referenced in commit 0f5112c - "fix(data): Fix Scroll Thrashing during Store Streaming (#9186)" on Feb 16, 2026, 2:30 PM

tobiu closed this issue on Feb 16, 2026, 2:31 PM

tobiu Feb 16, 2026, 2:32 PM

Input from Gemini 3 Pro:

✦ Implementation Update:

The final implementation differs from the initial proposal to handle edge cases correctly:

First Chunk: We detect if store.count === addedItems.length. If true, postChunkLoad is set to false. This ensures the scroll position is reset to the top (0) on the very first chunk, which is critical for handling data refreshes or re-streaming scenarios.

Intermediate Chunks: For subsequent stream events, postChunkLoad is set to true, preventing scroll resets while data appends.

Completion Event: The final load event fired by Store.load() (after the stream proxy finishes) now explicitly checks me.proxy?.ntype === 'proxy-stream'. If true, it sets postChunkLoad: true. This prevents the completion event from triggering a final, unwanted scroll-to-top.

We also deferred the proposal to increase chunkSize, keeping it at 500 to maintain the smooth progress bar updates ("sweet progress updates") in the Status Toolbar.