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	9311
title	Bug / Enhancement: Fix unstable sorting & enforce nulls at bottom
state	Closed
labels	bugenhancementaicore
assignees	tobiu
createdAt	Feb 26, 2026, 4:41 PM
updatedAt	Feb 26, 2026, 4:47 PM
githubUrl	https://github.com/neomjs/neo/issues/9311
author	tobiu
commentsCount	1
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Feb 26, 2026, 4:47 PM

Bug / Enhancement: Fix unstable sorting & enforce nulls at bottom

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

Closed v12.0.0 bugenhancementaicore

tobiu commented on Feb 26, 2026, 4:41 PM

Sorting columns with mapped data and missing values (like company in DevIndex) resulted in unstable, varying sort orders that seemingly "improved" the more times a sort was triggered.

This occurred due to two overlapping issues:

Soft Hydration Inconsistency: Neo.data.Store#resolveField was returning undefined for missing mapped keys on raw objects, while fully hydrated records correctly received their defaultValue (e.g., null).
JavaScript Sorting Transitivity: Neo.collection.Base and Neo.collection.Sorter relied on standard < and > operators. In JS, null and undefined evaluate as "equal" to strings (both < and > return false), breaking sorting transitivity and causing random scrambling of the array.

This ticket fixes the bug by introducing an enhancement to the framework's sorting paradigm: null and undefined values are now always pushed to the bottom of the collection, regardless of whether the sort direction is ASC or DESC.

Changes:

src/data/Store.mjs: Updated resolveField() to apply defaultValue if the raw value is undefined.
src/collection/Base.mjs: Added explicit == null isolation logic to doSort() to always push null/undefined values to the bottom.
src/collection/Sorter.mjs: Added explicit == null isolation logic to defaultSortBy() to always push null/undefined values to the bottom.
test/playwright/unit/collection/SortNull.spec.mjs: Added a new unit test to explicitly verify this behavior.

tobiu added the bug label on Feb 26, 2026, 4:41 PM

tobiu added the enhancement label on Feb 26, 2026, 4:41 PM

tobiu added the ai label on Feb 26, 2026, 4:41 PM

tobiu added the core label on Feb 26, 2026, 4:41 PM

tobiu referenced in commit dc446b4 - "fix(core): Fix unstable sorting & enforce nulls at bottom (#9311)" on Feb 26, 2026, 4:47 PM

tobiu assigned to @tobiu on Feb 26, 2026, 4:47 PM

tobiu Feb 26, 2026, 4:47 PM

Input from Gemini 3.1 Pro:

✦ Successfully fixed and pushed to the dev branch in commit dc446b439.

Summary of Completion:

src/data/Store.mjs updated to correctly apply defaultValue during soft hydration resolveField().

src/collection/Base.mjs and src/collection/Sorter.mjs updated to strictly isolate null and undefined values and force them to the bottom of the collection during sort operations (both ASC and DESC), fixing the transitivity issue.

Added the test/playwright/unit/collection/SortNull.spec.mjs unit test to prevent regression.

tobiu closed this issue on Feb 26, 2026, 4:47 PM