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	9435
title	TreeStore: Fix visible projection for dynamic child additions to expanded parents
state	Closed
labels	bugai
assignees	tobiu
createdAt	Mar 10, 2026, 10:17 PM
updatedAt	Mar 10, 2026, 11:14 PM
githubUrl	https://github.com/neomjs/neo/issues/9435
author	tobiu
commentsCount	1
parentIssue	9404
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Mar 10, 2026, 11:14 PM

TreeStore: Fix visible projection for dynamic child additions to expanded parents

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

Closed v12.1.0 bugai

tobiu commented on Mar 10, 2026, 10:17 PM

When a new child node is dynamically added to a TreeStore and its parent is already expanded, the splice() method fails to correctly project this new child into the flat _items array at the correct hierarchical index.

Currently, the logic either misses the child entirely (if the parent is already in #allRecordsMap) or relies on Collection.splice without an index, which appends the node to the very end of the array, destroying the visual tree structure.

We need to calculate the precise insertion index for visibleToAdd nodes, or restructure the insertion logic to ensure they appear sequentially after their parent and preceding siblings in the flat view.

tobiu assigned to @tobiu on Mar 10, 2026, 10:17 PM

tobiu added the bug label on Mar 10, 2026, 10:17 PM

tobiu added the ai label on Mar 10, 2026, 10:17 PM

tobiu added parent issue #9404 on Mar 10, 2026, 10:17 PM

tobiu referenced in commit 4d16914 - "fix(data.TreeStore): Fix visible projection for dynamic child additions to expanded, sorted, and filtered trees (#9435) on Mar 10, 2026, 11:13 PM

tobiu Mar 10, 2026, 11:13 PM

Input from Gemini 3.1 Pro:

✦ The code has been successfully committed and pushed!

The underlying issue wasn't just the logic for calculating the insertion index, but also a major symbol mismatch between Collection.Base and TreeStore that caused TreeStore.splice() to fail to detect when filters were active.

Summary of Fixes:

Unfiltered/Unsorted Additions: Implemented getInsertIndexForNode to accurately calculate the flat projection index based on the preceding sibling's deep visible descendants, ensuring nodes are inserted perfectly after their parent in the _items array.

Filtered Additions: Standardized all state symbols (isFiltered, isSorted, updatingIndex) to use Symbol.for() globally across Collection.Base and TreeStore.mjs. TreeStore.splice() now correctly intercepts dynamic additions during filtered states and triggers a clean me.filter() projection rebuild without corrupting the O(1) maps.

Sorted Additions: Confirmed via new unit tests that the existing autoSort mechanic cleanly relies on TreeStore.doSort() to handle positional insertion for sorted tree stores.

I will close this ticket now.

tobiu closed this issue on Mar 10, 2026, 11:14 PM

tobiu referenced in commit 3f315d6 - "docs(data.TreeStore): Enhance JSDoc for getInsertIndexForNode (#9435)" on Mar 10, 2026, 11:20 PM