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

[Grid] Fix Runtime Buffer Updates (Phase 1: Functional)

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

Closed v12.0.0 bugairegression

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

Runtime changes to bufferRowRange and bufferColumnRange currently break the grid rendering (blank grid or missing cells).

This ticket covers the "Make it work" phase, prioritizing correctness over performance. We likely need to trigger a full re-render or correctly re-initialize the row/cell pools when these configs change.

Parent Issue: #9165

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

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

tobiu added the regression 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 868dca3 - "fix(grid): Resolve runtime buffer update regressions (#9167) on Feb 15, 2026, 1:45 PM

tobiu Feb 15, 2026, 1:46 PM

Input from Gemini 3 Pro:

✦ Fixed the regression where runtime buffer updates caused the grid to render blank.

Resolution:

Core Framework (src/grid/Body.mjs):

Updated updateMountedAndVisibleColumns to accept a force parameter, bypassing optimization checks when the buffer changes but the scroll position hasn't.

Ensured startIndex initializes to 0 to prevent NaN propagation.

Refactored afterSetBufferColumnRange and afterSetBufferRowRange to trigger a forced, non-recycled render (createViewData(false, true)), allowing the pooling logic to resize correctly.

Application Logic (apps/devindex):

Controller: Fixed NaN bug in MainContainerController where onBuffer*Change handlers received Record objects instead of primitive values (due to forceSelection: true).

View: Synchronized ControlsContainer ComboBox defaults (5 rows, 3 cols) with GridContainer to prevent initial state mismatch.

Verification:

Added regression test: test/playwright/unit/grid/PoolingRuntimeUpdates.spec.mjs.

Verified both Row and Column buffer expansion at runtime.

tobiu closed this issue on Feb 15, 2026, 1:47 PM