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	9304
title	Fix: Enforce static state bindings for pooled Component columns (Memory Leak)
state	Closed
labels	bugai
assignees	tobiu
createdAt	Feb 25, 2026, 7:29 PM
updatedAt	Feb 25, 2026, 7:30 PM
githubUrl	https://github.com/neomjs/neo/issues/9304
author	tobiu
commentsCount	1
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Feb 25, 2026, 7:30 PM

Fix: Enforce static state bindings for pooled Component columns (Memory Leak)

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

Closed v12.0.0 bugai

tobiu commented on Feb 25, 2026, 7:29 PM

When using Neo.grid.column.Component with useBindings: true, the framework previously called gridContainer.body.getStateProvider()?.createBindings(component) every time a cell was rendered.

Because Neo.grid.Row pools its cell components, scrolling fast through a buffered grid called cellRenderer thousands of times on the same component instances. This caused Neo.state.Provider to attach a new reactive Effect to those same components every time they recycled, leading to a massive memory leak and severe performance degradation.

This fix:

Moves the createBindings call to only execute ONCE when the pooled component is first instantiated.
Explicitly deletes componentConfig.bind during row recycling to prevent the config system from triggering it.
Updates the JSDoc to clearly warn developers that bindings on pooled components are evaluated statically exactly once, and must only be used for global/hierarchical UI state (like theme or animateVisuals), never for dynamically iterating record data.

tobiu added the bug label on Feb 25, 2026, 7:29 PM

tobiu added the ai label on Feb 25, 2026, 7:29 PM

tobiu referenced in commit e8176bf - "fix(grid): Enforce static state bindings for pooled Component columns (#9304)" on Feb 25, 2026, 7:29 PM

tobiu Feb 25, 2026, 7:29 PM

Input from Gemini 3.1 Pro:

✦ I have successfully enforced static state bindings for pooled Component columns in src/grid/column/Component.mjs.

The createBindings call is now safely restricted to the component instantiation phase, entirely eliminating the reactive Effect memory leak during grid scrolling. The JSDoc has also been updated with a clear performance warning about this limitation.

I've committed and pushed the changes. Marking this issue as resolved!

tobiu assigned to @tobiu on Feb 25, 2026, 7:30 PM

tobiu closed this issue on Feb 25, 2026, 7:30 PM

tobiu referenced in commit 8e6e4b8 - "refactor(grid): Migrate Sparkline to useBindings (#9301, #9304)" on Feb 25, 2026, 7:32 PM