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	8886
title	fix: Ensure Collection.clear() clears allItems in filtered state
state	Closed
labels	bugaitesting
assignees	tobiu
createdAt	Jan 26, 2026, 8:26 PM
updatedAt	Jan 26, 2026, 8:30 PM
githubUrl	https://github.com/neomjs/neo/issues/8886
author	tobiu
commentsCount	2
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Jan 26, 2026, 8:30 PM

fix: Ensure Collection.clear() clears allItems in filtered state

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

Closed v11.24.0 bugaitesting

tobiu commented on Jan 26, 2026, 8:26 PM

The Collection.clear() method had a flaw when used on a filtered collection. It only cleared the visible items (this.items / this._items) but failed to clear the underlying allItems collection, which stores the full, unfiltered dataset.

This behavior led to data corruption and retention issues, particularly in scenarios involving:

Reloading Stores: When a filtered store was reloaded (cleared and then populated with new data), the old, hidden items remained in allItems. This could cause allItems to grow indefinitely or contain mixed state from previous loads.
Massive Data: In the Big Data Grid example, this manifested as inconsistencies when switching between large datasets while filters were active.

Resolution: The clear() method in src/collection/Base.mjs has been updated to explicitly call this.allItems?.clear() before clearing the local items.

Regression Test: A new unit test file test/playwright/unit/collection/MassiveData.spec.mjs has been added. It specifically targets:

Adding 10k+ items to a store.
Applying filters.
Clearing the store.
Verifying that allItems is correctly emptied.
Reloading data and ensuring counts match expectation (no ghost items).
Verifying that adding items to a filtered collection correctly updates allItems (data loss check).

tobiu added the bug label on Jan 26, 2026, 8:26 PM

tobiu added the ai label on Jan 26, 2026, 8:26 PM

tobiu added the testing label on Jan 26, 2026, 8:26 PM

tobiu referenced in commit cf4ddf4 - "fix: Ensure Collection.clear() clears allItems in filtered state (#8886)" on Jan 26, 2026, 8:26 PM

tobiu assigned to @tobiu on Jan 26, 2026, 8:28 PM

tobiu Jan 26, 2026, 8:28 PM

Input from Gemini 3 Pro:

✦ I have implemented the fix and added the regression test.

Changes:

src/collection/Base.mjs: Updated clear() to invoke this.allItems?.clear() before splicing. This ensures that the source collection (containing hidden/filtered items) is also wiped.

test/playwright/unit/collection/MassiveData.spec.mjs: Added a comprehensive test suite that:

Adds 10,000 items to a store.

Applies a filter.

Clears the store.

Verifies count is 0.

Adds another 10,000 items.

Verifies that allItems correctly reflects 10,000 items (not 20,000 or a corrupted state).

Checks for undefined items to ensure data integrity.

Verifies that adding a non-matching item to a filtered collection correctly updates allItems.

The test suite passes successfully.

tobiu referenced in commit 30f5d6d - "fix: Update clearSilent to also clear allItems in filtered collections (#8886)" on Jan 26, 2026, 8:29 PM

tobiu Jan 26, 2026, 8:29 PM

Input from Gemini 3 Pro:

✦ I have also updated clearSilent() in src/collection/Base.mjs to recursively clear allItems if it exists. This ensures consistency for silent clear operations as well.

tobiu closed this issue on Jan 26, 2026, 8:30 PM