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	9538
title	Enhance Collection.updateKey() to support filtered collections (allItems map)
state	Closed
labels	enhancementaicore
assignees	tobiu
createdAt	Mar 24, 2026, 9:49 AM
updatedAt	Mar 27, 2026, 10:08 AM
githubUrl	https://github.com/neomjs/neo/issues/9538
author	tobiu
commentsCount	1
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Mar 27, 2026, 10:08 AM

Enhance Collection.updateKey() to support filtered collections (allItems map)

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

Closed v12.1.0 enhancementaicore

tobiu commented on Mar 24, 2026, 9:49 AM

Objective

The newly added updateKey(item, newKey) method in Neo.collection.Base (introduced via PR #9536) correctly updates the primary map without mutating the _items array. However, it fails to account for filtered collections.

When a collection is filtered, it creates an allItems collection to store the unfiltered dataset. If a key is updated while the collection is filtered, the map inside me.allItems must also be updated to prevent a stale key mapping.

Proposal

Update src/collection/Base.mjs -> updateKey() to check for the existence of me.allItems. If it exists, perform the identical map delete/set operation on me.allItems.map.

// Pseudo-code concept:
if (me.allItems) {
    me.allItems.map.delete(oldKey);
    me.allItems.map.set(newKey, item);
}

tobiu added the enhancement label on Mar 24, 2026, 9:49 AM

tobiu added the ai label on Mar 24, 2026, 9:49 AM

tobiu added the core label on Mar 24, 2026, 9:49 AM

tobiu cross-referenced by PR #9536 on Mar 24, 2026, 9:52 AM

tobiu referenced in commit c133b97 - "feat: Enhance Collection.updateKey() to support filtered collections (#9538)" on Mar 27, 2026, 10:08 AM

tobiu Mar 27, 2026, 10:08 AM

Input from Antigravity:

◆ I have completed the implementation for this issue.

Summary of Changes:

Modified updateKey(item, newKey) in src/collection/Base.mjs to accurately propagate key changes to allItems.map when a collection is filtered.

Added comprehensive unit tests in test/playwright/unit/collection/Base.spec.mjs verifying that updateKey() handles both unfiltered and filtered collections seamlessly without breaking the indexing map.

Successfully executed npm run test-unit against the base collection specification, recording 9/9 passes.

The changes have been pushed to the remote repository and the issue is now complete.

tobiu assigned to @tobiu on Mar 27, 2026, 10:08 AM

tobiu closed this issue on Mar 27, 2026, 10:08 AM