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	9425
title	Refactor Tree cell component architecture for performance
state	Closed
labels	enhancementrefactoringperformancegrid
assignees	tobiu
createdAt	Mar 9, 2026, 9:22 PM
updatedAt	Mar 9, 2026, 9:23 PM
githubUrl	https://github.com/neomjs/neo/issues/9425
author	tobiu
commentsCount	1
parentIssue	9404
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Mar 9, 2026, 9:23 PM

Refactor Tree cell component architecture for performance

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

Closed v12.1.0 enhancementrefactoringperformancegrid

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

Goal

To optimize the Neo.grid.column.component.Tree cell component by eliminating redundant state configs and consolidating VDOM updates, improving rendering performance during fast scrolling.

Context

The initial implementation of the Tree cell component duplicated record data (depth, expanded, isLeaf) into separate reactive configs. This resulted in poor performance during row recycling, as updating a single record would trigger multiple consecutive afterSet hooks and redundant VDOM update() calls. It also created unnecessary overhead in the parent grid.column.Tree which had to manually unpack the record into these configs.

Requirements

Remove Redundant State: Remove depth_, expanded_, and isLeaf_ from grid.column.component.Tree. The record_ is the single source of truth.
Consolidate Updates: Move all structural styling logic (indentation depth, toggle icons) into a single afterSetRecord hook, ensuring only one me.update() is called per recycle.
Simplify Column Feed: Update applyRecordConfigs in grid.column.Tree to only pass the extracted value, relying on the component to read its own bound record.
Fix Event Target: Update onToggleClick to cleanly access the store via me.parent.gridContainer.

tobiu assigned to @tobiu on Mar 9, 2026, 9:22 PM

tobiu added the enhancement label on Mar 9, 2026, 9:22 PM

tobiu added the refactoring label on Mar 9, 2026, 9:22 PM

tobiu added the performance label on Mar 9, 2026, 9:22 PM

tobiu added the grid label on Mar 9, 2026, 9:22 PM

tobiu added parent issue #9404 on Mar 9, 2026, 9:22 PM

tobiu referenced in commit 1ab27f9 - "refactor(grid): Clean up Tree cell component architecture (#9425)" on Mar 9, 2026, 9:23 PM

tobiu Mar 9, 2026, 9:23 PM

Input from Gemini 3.1 Pro:

✦ I have rewritten the Tree cell component to rely purely on the afterSetRecord hook.

All redundant state configs (depth_, expanded_, isLeaf_) have been removed.

VDOM updates (indent style, toggle classes) are now batched into a single method during row recycling.

applyRecordConfigs was simplified to only pass down value.

Committed and pushed. Closing ticket.

tobiu closed this issue on Mar 9, 2026, 9:23 PM