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	9168
title	[Grid] Optimize Runtime Buffer Updates (Phase 2: Performance)
state	Closed
labels	enhancementaiperformance
assignees	tobiu
createdAt	Feb 15, 2026, 1:00 PM
updatedAt	Feb 15, 2026, 2:26 PM
githubUrl	https://github.com/neomjs/neo/issues/9168
author	tobiu
commentsCount	1
parentIssue	9165
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Feb 15, 2026, 2:26 PM

[Grid] Optimize Runtime Buffer Updates (Phase 2: Performance)

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

Closed v12.0.0 enhancementaiperformance

tobiu commented on Feb 15, 2026, 1:00 PM

After fixing the functional regression in Phase 1, we need to optimize the runtime buffer updates. The goal is to avoid a full re-render when changing bufferRowRange or bufferColumnRange. We should implement smarter pooling expansion/contraction to preserve existing DOM nodes where possible.

Parent Issue: #9165

tobiu added the enhancement label on Feb 15, 2026, 1:00 PM

tobiu added the ai label on Feb 15, 2026, 1:00 PM

tobiu added the performance label on Feb 15, 2026, 1:00 PM

tobiu assigned to @tobiu on Feb 15, 2026, 1:01 PM

tobiu added parent issue #9165 on Feb 15, 2026, 1:01 PM

tobiu referenced in commit 09c2641 - "fix(grid): Optimize buffer updates and prevent view clipping (#9168) on Feb 15, 2026, 2:25 PM

tobiu Feb 15, 2026, 2:26 PM

Input from Gemini 3 Pro:

✦ Implemented performance optimizations and fixed a visibility regression.

Changes:

Optimization (Phase 2): Removed force=true from buffer updates to allow row recycling, significantly reducing VDOM churn.

Fix: Addressed a regression where reducing bufferRowRange after deep scrolling caused visible rows to vanish.

Cause: The startIndex optimization (hysteresis) could leave startIndex stale relative to scrollTop. Reducing the buffer tightened the window around this stale index, clipping current rows.

Solution: In afterSetBufferRowRange, conditionally resynchronize startIndex if the drift exceeds the new buffer size.

Verification:

Updated test/playwright/unit/grid/PoolingRuntimeUpdates.spec.mjs with deep scrolling reproduction cases. All passed.

tobiu closed this issue on Feb 15, 2026, 2:26 PM

tobiu cross-referenced by #9169 on Feb 15, 2026, 2:51 PM