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	9406
title	Create `Neo.data.TreeStore`
state	Closed
labels	enhancementaicore
assignees	tobiu
createdAt	Mar 9, 2026, 11:44 AM
updatedAt	Mar 9, 2026, 2:38 PM
githubUrl	https://github.com/neomjs/neo/issues/9406
author	tobiu
commentsCount	3
parentIssue	9404
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Mar 9, 2026, 2:38 PM

Create `Neo.data.TreeStore`

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

Closed v12.1.0 enhancementaicore

tobiu commented on Mar 9, 2026, 11:44 AM

Goal

Create a specialized store to manage hierarchical data and provide a flattened view for virtual scrolling.

Details

Location: src/data/TreeStore.mjs
Extends: Neo.data.Store
Internal State:
- Implement a #childrenMap (Map) keyed by parentId to enable O(1) child lookups.
Flattened View:
- The store must maintain the full data structure but expose a flattened 1D array of only the visible nodes (root nodes + children of expanded nodes) to the grid's virtual scroller.
Core Methods:
- expand(nodeId): Updates node state, retrieves children, injects them into the flattened view, and fires a mutate event.
- collapse(nodeId): Reverses the expansion, recursively removing visible descendants from the flattened array.
- toggle(nodeId): Toggles the expanded state.
- loadData(data): Overridden to populate the internal #childrenMap.
Config:
- singleExpand (Boolean): Support for accordion-style expansion (expanding one node collapses siblings).

tobiu added the enhancement label on Mar 9, 2026, 11:44 AM

tobiu added the ai label on Mar 9, 2026, 11:44 AM

tobiu added the core label on Mar 9, 2026, 11:44 AM

tobiu added parent issue #9404 on Mar 9, 2026, 11:44 AM

tobiu Mar 9, 2026, 12:09 PM

Input from Gemini 3.1 Pro:

✦ Implementation Guidance for Agents:

The core architectural mandate for the TreeStore is to allow the Neo.grid.Body virtual scroller to function without modification.

The Flattened View: The GridBody iterates over the store's items array. Therefore, the TreeStore MUST override or manage its internal _items array to only contain the currently visible nodes (root nodes + children of expanded nodes).

O(1) Lookups: You must implement a private #childrenMap = new Map() keyed by parentId to ensure that when a node is expanded, retrieving its children to inject into the flattened view is an O(1) operation. Do not use store.filter() to find children during an expand operation.

Mutations: Expanding or collapsing a node should update the flattened view and fire a mutate event so the grid automatically recalculates aria-rowcount and scrollbar height.

Important Files to Reference:

src/collection/Base.mjs (Understand splice and mutate events).

src/grid/Body.mjs -> createViewData() (Understand how the grid maps the 1D array to the DOM).

tobiu assigned to @tobiu on Mar 9, 2026, 12:10 PM

tobiu cross-referenced by #9413 on Mar 9, 2026, 12:33 PM

tobiu referenced in commit aec7125 - "feat: Add Neo.data.TreeStore (#9406) on Mar 9, 2026, 2:38 PM

tobiu Mar 9, 2026, 2:38 PM

Input from Gemini 3.1 Pro:

✦ Implemented Neo.data.TreeStore with the "Splice Approach".

Introduces #childrenMap and #allRecordsMap for data integrity and fast lookup.

The internal _items array (used by GridBody) dynamically flattens only the visible nodes via Collection.splice().

Implemented expand(), collapse(), and toggle() functions for fast virtual scrolling recalculation without a full store filter.

Added singleExpand behavior.

Changes pushed to dev.

tobiu Mar 9, 2026, 2:38 PM

Implemented Neo.data.TreeStore. Pushed to dev.

tobiu closed this issue on Mar 9, 2026, 2:38 PM

Create Neo.data.TreeStore

Goal

Details

Create `Neo.data.TreeStore`