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	9448
title	TreeGrid Component pooling accumulates `is-leaf` class leading to visual bugs
state	Closed
labels	bugaigrid
assignees	tobiu
createdAt	Mar 12, 2026, 12:29 PM
updatedAt	Mar 12, 2026, 12:31 PM
githubUrl	https://github.com/neomjs/neo/issues/9448
author	tobiu
commentsCount	1
parentIssue	9404
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Mar 12, 2026, 12:31 PM

TreeGrid Component pooling accumulates `is-leaf` class leading to visual bugs

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

Closed v12.1.0 bugaigrid

tobiu commented on Mar 12, 2026, 12:29 PM

Description

In Neo.grid.column.component.Tree, the updateIconCls() method mutates the class array using cls.push('is-leaf') inside multiple afterSet... hooks (e.g. afterSetIsLeaf, afterSetCollapsed, etc). When multiple configs change simultaneously (e.g., when a grid cell is recycled by the virtual scroller for a different record), updateIconCls() runs synchronously multiple times before the vdom update is flushed.

This causes state classes like is-expanded and is-leaf to be pushed multiple times into the cls array. Later, when the component is recycled again, NeoArray.remove() only removes the first instance of these duplicate classes. This leads to conflicting classes persisting on the DOM node (e.g. <div class="neo-tree-toggle is-leaf is-expanded">), causing folder icons to disappear.

Solution

Use NeoArray.add(cls, ...) instead of cls.push(...) in Tree.mjs to ensure the state classes are unique within the array, preventing the accumulator bug during rapid config updates.

tobiu added the bug label on Mar 12, 2026, 12:29 PM

tobiu added the ai label on Mar 12, 2026, 12:29 PM

tobiu added the grid label on Mar 12, 2026, 12:29 PM

tobiu assigned to @tobiu on Mar 12, 2026, 12:30 PM

tobiu added parent issue #9404 on Mar 12, 2026, 12:30 PM

tobiu referenced in commit 9095a0d - "fix(grid): prevent duplicate state classes in Tree component during pooling (#9448)" on Mar 12, 2026, 12:31 PM

tobiu Mar 12, 2026, 12:31 PM

Input from Gemini 3.1 Pro:

✦ The bug was diagnosed and fixed. The issue was that updateIconCls() in src/grid/column/component/Tree.mjs was using .push() on the cls array inside multiple afterSet... hooks. During rapid state changes (e.g. Row Pooling where the same component gets multiple new configs like collapsed and isLeaf), .push() accumulated multiple instances of the state classes. Later, NeoArray.remove() only removes the first instance, leaving stale classes on the DOM node. Replacing .push() with NeoArray.add() ensures only unique classes are kept, fixing the visual glitch in the tree grid.

Test test/playwright/e2e/GridTree.spec.mjs now passes successfully.

tobiu closed this issue on Mar 12, 2026, 12:31 PM

tobiu cross-referenced by #9412 on Mar 12, 2026, 12:41 PM

TreeGrid Component pooling accumulates is-leaf class leading to visual bugs

Description

Solution

TreeGrid Component pooling accumulates `is-leaf` class leading to visual bugs