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	9069
title	Refactor: Collection.Base to use getKey() hook for Turbo Mode Support
state	Closed
labels	bugcore
assignees	tobiu
createdAt	Feb 9, 2026, 3:48 AM
updatedAt	Feb 9, 2026, 3:55 AM
githubUrl	https://github.com/neomjs/neo/issues/9069
author	tobiu
commentsCount	1
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Feb 9, 2026, 3:55 AM

Refactor: Collection.Base to use getKey() hook for Turbo Mode Support

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

Closed v12.0.0 bugcore

tobiu commented on Feb 9, 2026, 3:48 AM

Problem: accesses directly. In Turbo Mode (Store), we use mapped keys (e.g. but raw data has ). Direct access returns , causing the Collection to generate negative IDs (, ) for items.

Solution:

Refactor : Introduce method (defaulting to direct access).
Update : Replace all internal direct key access with .
: Ensure its existing override correctly handles the Reverse Mapping (Canonical -> Raw) logic.

Result: The Collection will correctly resolve keys from Raw Objects even when using Canonical Key Properties, fixing the Grid ID regression without breaking Selection Models.

tobiu assigned to @tobiu on Feb 9, 2026, 3:48 AM

tobiu added the bug label on Feb 9, 2026, 3:48 AM

tobiu added the core label on Feb 9, 2026, 3:48 AM

tobiu changed title from Fix: Grid IDs Regression & Store.getKey Reverse Mapping Support to Refactor: Collection.Base to use getKey() hook for Turbo Mode Support on Feb 9, 2026, 3:50 AM

tobiu Feb 9, 2026, 3:55 AM

Input from Gemini 3 Pro:

✦ I have resolved the regression where the Grid was displaying negative IDs (-1, -2).

Analysis:

Root Cause: Neo.collection.Base accessed item[this.keyProperty] directly. In "Turbo Mode" (Store), keyProperty is 'login', but the raw item only has 'l'. Direct access returned undefined, causing the Collection to generate new negative IDs.

Solution: Refactored Neo.collection.Base to use a getKey(item) method (defaulting to direct access). This allows Neo.data.Store (which overrides getKey) to inject its smart "Reverse Mapping" logic (added in #9067).

Changes:

Refactored src/collection/Base.mjs: Replaced direct keyProperty access with getKey(item).

App Config: Contributors.mjs remains keyProperty: 'login' (canonical), ensuring architectural correctness.

Result: The Grid now correctly identifies records using the mapped key (l -> login), displaying positive IDs and allowing correct selection behavior.

tobiu referenced in commit 549c442 - "Refactor: Collection.Base to use getKey() hook for Turbo Mode Support (#9069)" on Feb 9, 2026, 3:55 AM

tobiu closed this issue on Feb 9, 2026, 3:55 AM