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	9067
title	Fix: Resolve Mapped KeyProperty Conflict in Turbo Mode via Store.getKey()
state	Closed
labels	bugcore
assignees	tobiu
createdAt	Feb 9, 2026, 3:11 AM
updatedAt	Feb 9, 2026, 3:44 AM
githubUrl	https://github.com/neomjs/neo/issues/9067
author	tobiu
commentsCount	1
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Feb 9, 2026, 3:44 AM

Fix: Resolve Mapped KeyProperty Conflict in Turbo Mode via Store.getKey()

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

Closed v12.0.0 bugcore

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

Resolve keyProperty access conflicts when using Mapped Fields in Turbo Mode (autoInitRecords: false).

The Problem:

Turbo Mode: Store holds raw objects. keyProperty points to the raw data key (e.g. 'l'). rawItem['l'] works.
Lazy Instantiation: When accessed, raw objects become Records. RecordFactory creates getters for canonical field names (e.g. login), but NOT for mapped source keys. record['l'] is undefined.
Selection Model: Uses record[store.getKeyProperty()]. If keyProperty is 'l', this fails on instantiated records.

The Fix:

Neo.data.Store#getKey(item): Implement a helper method to resolve the key regardless of item type.
- Try item[keyProp].
- If undefined & item is Record, try item.get(keyProp).
Refactor Selection Models: Update RowModel (and others) to use store.getKey(record) instead of direct access.

Goal: Transparently support mapped key properties in mixed Raw/Record environments.

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

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

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

tobiu Feb 9, 2026, 3:36 AM

Input from Gemini 3 Pro:

✦ I have resolved the critical keyProperty conflict that was breaking Grid selection in Turbo Mode.

The Fix:

Architecture: Implemented Neo.data.Store#getKey(item).

This helper acts as a bridge between Raw Objects (Turbo Mode) and Record Instances.

It supports Reverse Mapping Lookup: If the Store uses a canonical key (e.g. login) but the raw item only has the source key (e.g. l), it resolves the correct value using the Model definition.

Refactoring: Updated Row.mjs and all SelectionModel classes to use store.getKey(record) instead of direct property access (record[key]), preventing undefined lookups on instantiated records.

App Config: Updated DevRank.store.Contributors to use the correct canonical keyProperty: 'login' instead of the raw 'l', ensuring architectural consistency.

Outcome:

Selection works correctly for both Raw Objects (Turbo) and Instantiated Records.

"All Rows Selected" bug is eliminated (no more undefined === undefined matches).

tobiu referenced in commit bab630b - "Fix: Resolve Mapped Key Conflict via Store.getKey() & Canonical Config (#9067)" on Feb 9, 2026, 3:37 AM

tobiu referenced in commit 2060f50 - "Fix: Update Grid Body getLogicalCellId to use Store.getKey (#9067)" on Feb 9, 2026, 3:37 AM

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

tobiu cross-referenced by #9069 on Feb 9, 2026, 3:55 AM