What is the Neural Link?

The Neural Link is a bi-directional bridge that connects AI agents directly to the Neo.mjs runtime. It lets agents inspect the Scene Graph, component state, event listeners, computed styles, and DOM rectangles, and mutate the running application in real time.

Why is Neo.mjs called an Application Engine instead of a framework?

Neo.mjs maintains persistent application objects in a worker-backed Scene Graph instead of compiling application state away into ephemeral DOM nodes. That architecture enables multi-window orchestration, runtime permutation, and deep AI introspection.

What is Context Engineering?

Context Engineering shapes the information and tool environment around AI agents. Neo.mjs implements it through Knowledge Base, Memory Core, GitHub Workflow, and Neural Link MCP servers for frontier harnesses, plus a File System MCP server for internal Neo.ai.Agent local loops.

What is the Neo.mjs Agent OS?

The Neo.mjs Agent OS is the repository Brain: source code and services for Memory Core, Knowledge Base, Active Hybrid GraphRAG, DreamService, Golden Path synthesis, A2A coordination, and Neural Link tooling.

Frontmatter

id	9424
title	Optimize `cellPoolSize` calculation in `grid.Body` to prevent DOM waste
state	Closed
labels	enhancementperformancecoregrid
assignees	tobiu
createdAt	Mar 9, 2026, 9:03 PM
updatedAt	Mar 9, 2026, 9:05 PM
githubUrl	https://github.com/neomjs/neo/issues/9424
author	tobiu
commentsCount	1
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
contentTrust
projected
quarantined	0
signals	[]
blockedBy	[]
blocking	[]
closedAt	Mar 9, 2026, 9:05 PM

Optimize `cellPoolSize` calculation in `grid.Body` to prevent DOM waste

Closed v12.1.0/archive-v12-1-0-chunk-1 enhancementperformancecoregrid

tobiu commented on Mar 9, 2026, 9:03 PM

Goal

To dynamically calculate the exact required cellPoolSize in Neo.grid.Body based on visible columns and buffer range, rather than relying on a hardcoded default that wastes DOM elements in small grids.

Context

Currently, Neo.grid.Body sets cellPoolSize_: 20 by default. In updateMountedAndVisibleColumns(), the pool only ever grows (by +5) if the visible columns exceed the pool size. This means a simple grid with only 3 columns still generates and manages 20 cells per row in the DOM, which is a massive waste of VDOM generation and reconciliation resources when horizontal scrolling isn't even active.

Requirements

Change the default cellPoolSize_ to null.
Update updateMountedAndVisibleColumns() to calculate the exact newPoolSize as endIndex - startIndex + 1.
Ensure the state is updated accurately if the new pool size differs from the current pool size, allowing the grid to shrink its pool if the total column count or viewport width decreases.

tobiu Mar 9, 2026, 9:05 PM

Input from Gemini 3.1 Pro:

✦ The hardcoded cellPoolSize_: 20 default has been changed to null, and updateMountedAndVisibleColumns now dynamically calculates the exact pool size required based on the total width/count of the mounted columns.

This prevents massive DOM bloat in simple grids (e.g. rendering 3 actual cells and 17 hidden pool cells).

Fix has been committed and pushed. Closing as complete.

Optimize cellPoolSize calculation in grid.Body to prevent DOM waste

Goal

Context

Requirements

Optimize `cellPoolSize` calculation in `grid.Body` to prevent DOM waste