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	9115
title	Optimize Store Streaming and Progressive Loading
state	Closed
labels	performancecore
assignees	tobiu
createdAt	Feb 12, 2026, 7:18 PM
updatedAt	Feb 12, 2026, 7:21 PM
githubUrl	https://github.com/neomjs/neo/issues/9115
author	tobiu
commentsCount	1
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Feb 12, 2026, 7:21 PM

Optimize Store Streaming and Progressive Loading

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

Closed v12.0.0 performancecore

tobiu commented on Feb 12, 2026, 7:18 PM

Refactor Neo.data.Store and Neo.data.proxy.Stream to optimize progressive loading and prevent UI blocking.

Key Changes:

Eliminate Duplicate Load Events: Remove manual load event firing in Store.onData. Rely on onCollectionMutate to trigger load events naturally when data is added, preventing double-firing for every chunk.
Unblock UI during Streaming: Introduce await me.timeout(5) in the Stream proxy's read loop. This yields control to the App Worker's event loop, allowing it to process VDOM updates and other events while parsing a large stream.
Track Streaming State: Introduce isStreaming flag on the Store (managed via the Proxy) to distinguish between intermediate progressive updates and the final load completion.
Base Proxy Enhancement: Add store config to Neo.data.proxy.Base to give proxies direct access to their owner store.

Goal: Ensure smooth, progressive rendering for large datasets (e.g., DevIndex) without freezing the UI.

tobiu added the performance label on Feb 12, 2026, 7:18 PM

tobiu added the core label on Feb 12, 2026, 7:18 PM

tobiu assigned to @tobiu on Feb 12, 2026, 7:19 PM

tobiu referenced in commit 4b1e3c3 - "feat: Optimize Store Streaming and Progressive Loading (#9115)" on Feb 12, 2026, 7:21 PM

tobiu Feb 12, 2026, 7:21 PM

Input from Gemini 3 Pro:

✦ I have completed the optimizations for store streaming and progressive loading.

Changes:

Eliminated Duplicate Load Events: Removed the manual fire('load') call in Neo.data.Store.onData. The store now relies on the mutate event (triggered by add()) to fire load events via onCollectionMutate, preventing double-firing for every data chunk.

Unblocked UI during Streaming: Added await me.timeout(5) to the Neo.data.proxy.Stream read loop. This yields control to the App Worker's event loop, allowing VDOM updates and other events to be processed during large stream parsing.

Tracked Streaming State: Introduced isStreaming logic in Neo.data.Store.load and updated onCollectionMutate to include an isLoading flag in the load event based on this state.

Base Proxy Enhancement: Added the store config to Neo.data.proxy.Base to ensure proxies have direct access to their owner store.

These changes ensure that the DevIndex grid renders smoothly and progressively as data streams in, without freezing the UI.

tobiu closed this issue on Feb 12, 2026, 7:21 PM