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	9135
title	Implement Safe Purge for Invalid Users in DevIndex Updater
state	Closed
labels	bugenhancementai
assignees	tobiu
createdAt	Feb 13, 2026, 3:13 AM
updatedAt	Feb 13, 2026, 3:16 AM
githubUrl	https://github.com/neomjs/neo/issues/9135
author	tobiu
commentsCount	1
parentIssue	9106
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Feb 13, 2026, 3:16 AM

Implement Safe Purge for Invalid Users in DevIndex Updater

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

Closed v12.0.0 bugenhancementai

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

We need a mechanism to purge invalid entities (Organizations, deleted users) from the tracker.json index while ensuring we don't accidentally delete valid users due to API glitches.

The "Safe Purge" Protocol:

Trigger: Updater.mjs catches a fatal error (Could not resolve to a User or NOT_FOUND).
Safety Check: Check if the user exists in users.jsonl (Rich Data Store).
- If Exists: This implies the user was valid in the past. Treat the 404 as suspicious (glitch, rename, suspension). Action: Move to Penalty Box (failed.json) for manual review. Do NOT delete.
- If NOT Exists: The user has never been indexed. It is likely a "Bad Seed" (Org, Bot, Typo) that leaked into the tracker. Action: Mark for deletion ({ delete: true }) in tracker.json.

Implementation:

Modify apps/devindex/services/Updater.mjs inside processBatch.
Load users.jsonl (or use Storage.getUsers()) to perform the existence check.

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

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

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

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

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

tobiu referenced in commit 5694710 - "feat(devindex): Implement Safe Purge for invalid users (#9135)" on Feb 13, 2026, 3:16 AM

tobiu Feb 13, 2026, 3:16 AM

Input from Gemini 3 Pro:

✦ I have implemented the Safe Purge Protocol in Updater.mjs.

Self-Healing Logic:

Fatal Error Detection: The updater now catches "Could not resolve to a User" and "NOT_FOUND" errors.

Safety Check: It checks if the failed user exists in the rich data store (users.jsonl).

Bad Seed (New): If the user has no history, they are immediately Deleted from tracker.json. This cleans up leaked organizations like loomnetwork.

Fallen Hero (Existing): If the user has history, they are moved to the Penalty Box (failed.json) instead. This protects valid users who might be temporarily hidden or renamed from being accidentally wiped.

Documentation: I added a comprehensive JSDoc block to processBatch explaining this logic to ensure future maintainers understand the "Why" behind the deletion.

tobiu closed this issue on Feb 13, 2026, 3:16 AM