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	8887
title	fix: Collection.filter() should not clear allItems when restoring unfiltered state
state	Closed
labels	bugairegression
assignees	tobiu
createdAt	Jan 26, 2026, 8:54 PM
updatedAt	Jan 26, 2026, 8:56 PM
githubUrl	https://github.com/neomjs/neo/issues/8887
author	tobiu
commentsCount	1
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Jan 26, 2026, 8:56 PM

fix: Collection.filter() should not clear allItems when restoring unfiltered state

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

Closed v11.24.0 bugairegression

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

The recent fix for #8886 introduced a recursive clearSilent() that implicitly clears allItems. However, Collection.filter() uses clearSilent() internally when restoring the full dataset (when all filters are disabled). This causes allItems to be wiped out, resulting in data loss when un-filtering.

Resolution: Replace the clearSilent() call in src/collection/Base.mjs's filter() method with manual cleanup that only targets the current view's _items and map, leaving allItems intact.

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

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

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

tobiu referenced in commit 6b8c1b7 - "fix: Collection.filter() should not clear allItems when restoring unfiltered state (#8887)" on Jan 26, 2026, 8:56 PM

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

tobiu Jan 26, 2026, 8:56 PM

Input from Gemini 3 Pro:

✦ I have resolved the regression.

Fix Details: In src/collection/Base.mjs, the filter() method was updated. Instead of calling me.clearSilent() (which now recursively clears allItems due to the fix for #8886), I have inlined the logic to clear only the local _items and map along with resetting initialIndexCounter.

This ensures that when filter() restores the full dataset (un-filtering), it reads from the intact allItems collection instead of wiping it out first.

Verification:

npm run test-unit -- collection/Base (The failing test) -> PASSED

npm run test-unit -- collection/MassiveData (The original fix verification) -> PASSED

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