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	9137
title	Implement ID-Based Rename Handling for DevIndex
state	Closed
labels	enhancementai
assignees	tobiu
createdAt	Feb 13, 2026, 3:23 AM
updatedAt	Feb 13, 2026, 2:20 PM
githubUrl	https://github.com/neomjs/neo/issues/9137
author	tobiu
commentsCount	1
parentIssue	9106
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Feb 13, 2026, 2:20 PM

Implement ID-Based Rename Handling for DevIndex

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

Closed v12.0.0 enhancementai

tobiu commented on Feb 13, 2026, 3:23 AM

Currently, when a user changes their GitHub username, the DevIndex Updater fails with a 404 (Not Found) because it queries by the old login. This results in the user being moved to the Penalty Box and eventually deleted, while the new username might be rediscovered as a fresh user, losing history continuity.

The Solution: ID-Based Rename Recovery

Trigger: When fetchUserData(login) returns a 404/Not Found.
Lookup: Retrieve the immutable github_id (field i) from our local users.jsonl record for that login.
Recovery: Query the GitHub API using the ID (node(id: "...") or user(id: ...)) to find the current login.
Resolution:
- If Found (New Login):
  - Update tracker.json: Remove old key, add new key (preserve timestamp or reset).
  - Update users.jsonl: Update l (login) and n (name) fields.
  - Log the rename event.
- If Not Found: Confirm it is a deletion/suspension. Move to Penalty Box (as per existing logic).

This ensures we track the human, not just the handle.

tobiu added the enhancement label on Feb 13, 2026, 3:23 AM

tobiu added the ai label on Feb 13, 2026, 3:23 AM

tobiu assigned to @tobiu on Feb 13, 2026, 3:24 AM

tobiu added parent issue #9106 on Feb 13, 2026, 3:24 AM

tobiu referenced in commit b50101a - "feat: Implement ID-Based Rename Handling for DevIndex (#9137) on Feb 13, 2026, 2:15 PM

tobiu Feb 13, 2026, 2:16 PM

Input from Gemini 3 Pro:

✦ Implemented ID-Based Rename Handling for DevIndex.

Key Components:

GitHub Service (GitHub.mjs):

Added getLoginByDatabaseId(dbId): Queries the GraphQL API using the integer databaseId (stored in our users.jsonl as i) to resolve the current login.

Storage Service (Storage.mjs):

Added deleteUsers(logins): Efficiently removes a batch of users from the rich data store (users.jsonl). This is crucial for cleaning up the old/stale login records after a rename is detected.

Updater Service (Updater.mjs):

Enhanced processBatch with a Rename Detection Logic flow inside the error handler.

Trigger: When a user fetch fails with a fatal error (404/Not Found) AND we have a record of that user with a GitHub ID (i).

Resolution:

Queries GitHub for the new login using the ID.

If a new login is returned (and is different from the old one):

Prune Old: Marks the old login for deletion from tracker.json (via indexUpdates) and users.jsonl (via prunedLogins).

Fetch New: Immediately fetches data for the new login.

Persist New: Adds the new user data to results and indexUpdates.

Outcome: The system self-heals. The old record is replaced by the new one without losing continuity (other than the login key change).

This logic ensures that high-value users who rename their accounts are not lost or penalized.

tobiu closed this issue on Feb 13, 2026, 2:20 PM