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	9434
title	TreeStore: Decouple clearFilters() from legacy allItems pattern
state	Closed
labels	enhancementairefactoringarchitecture
assignees	tobiu
createdAt	Mar 10, 2026, 3:26 PM
updatedAt	Mar 10, 2026, 4:28 PM
githubUrl	https://github.com/neomjs/neo/issues/9434
author	tobiu
commentsCount	1
parentIssue	9404
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Mar 10, 2026, 4:28 PM

TreeStore: Decouple clearFilters() from legacy allItems pattern

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

Closed v12.1.0 enhancementairefactoringarchitecture

tobiu commented on Mar 10, 2026, 3:26 PM

Goal

Refactor clearFilters() in TreeStore to utilize the native _keptNodes masking logic rather than relying on Collection.Base's allItems cloning fallback.

Context

Standard Neo.data.Store filtering works by cloning the entire dataset into an allItems collection so it remembers the unfiltered state. Our custom TreeStore.filter() bypasses this because it relies entirely on #allRecordsMap as the ultimate source of truth, masking the projection using a _keptNodes Set. Currently, if a developer clears the filters, it might trigger the inherited Collection.Base logic, which expects allItems to exist.

Acceptance Criteria

Override clearFilters() in TreeStore.mjs.
The method should nullify or clear this._keptNodes.
The method should completely rebuild the flat _items projection (collectVisibleDescendants) from the root nodes.
Do not let it fallback to super.clearFilters() if that triggers allItems manipulation.
Fire a standard filter event with isFiltered: false.
Write a unit test verifying that clearFilters() successfully restores the entire visible tree hierarchy without data loss.

tobiu added the enhancement label on Mar 10, 2026, 3:26 PM

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

tobiu added the refactoring label on Mar 10, 2026, 3:26 PM

tobiu added the architecture label on Mar 10, 2026, 3:26 PM

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

tobiu assigned to @tobiu on Mar 10, 2026, 3:29 PM

tobiu referenced in commit e78c93b - "TreeStore: Decouple clearFilters() from legacy allItems pattern (#9434)" on Mar 10, 2026, 4:27 PM

tobiu Mar 10, 2026, 4:27 PM

Input from Gemini 3.1 Pro:

✦ I have overridden clearFilters() in TreeStore.mjs to decouple it from the legacy allItems pattern.

The new implementation simply clears me._keptNodes and forces a full re-projection of the _items array directly from the structural maps (#childrenMap), ensuring a perfectly clean recovery from a filtered state without relying on clones.

Bonus: I also uncovered and fixed a subtle bug where me.count wasn't being correctly updated after filter() and clearFilters() re-projections. Both methods now explicitly set me.count = me._items.length.

Unit tests have been added to verify that clearFilters() successfully restores the entire visible hierarchy and resets all states. The commit has been pushed to the dev branch.

tobiu closed this issue on Mar 10, 2026, 4:28 PM