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	9044
title	Fix: DevRank Updater Infinite Loop & Tracker Pruning
state	Closed
labels	bugai
assignees	tobiu
createdAt	Feb 7, 2026, 10:42 PM
updatedAt	Feb 7, 2026, 10:46 PM
githubUrl	https://github.com/neomjs/neo/issues/9044
author	tobiu
commentsCount	1
parentIssue	8930
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Feb 7, 2026, 10:46 PM

Fix: DevRank Updater Infinite Loop & Tracker Pruning

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

Closed v12.0.0 bugai

tobiu commented on Feb 7, 2026, 10:42 PM

Fix two critical issues in the DevRank update cycle:

Infinite Loop for Bots: The Updater currently skips adding indexUpdates for users that return null (bots/deleted). This leaves their lastUpdate as null in the tracker, causing Manager.runUpdate to re-select them immediately in the next run.
- Fix: In Updater.mjs, ensure indexUpdates is pushed even if fetchUserData returns null (set timestamp to now, or remove from tracker/add to blacklist).
Tracker Pruning: The Cleanup.mjs service currently does not prune low-value users from tracker.json, only from users.json. This means we keep tracking thousands of inactive users forever.
- Fix: In Cleanup.mjs, remove users from tracker.json if they do not meet the contribution threshold (and are not whitelisted).

Plan:

Refactor Updater.mjs: Ensure indexUpdates is populated for "SKIPPED (No Data/Bot)" cases.
Refactor Cleanup.mjs: Update the tracker filtering logic to respect the contribution threshold, effectively pruning the index.
Refactor Storage.mjs: Ensure case-insensitivity for logins to prevent duplicates.

tobiu added the bug label on Feb 7, 2026, 10:42 PM

tobiu added the ai label on Feb 7, 2026, 10:42 PM

tobiu added parent issue #8930 on Feb 7, 2026, 10:43 PM

tobiu assigned to @tobiu on Feb 7, 2026, 10:44 PM

tobiu referenced in commit 9f95633 - "fix: DevRank Updater Infinite Loop & Tracker Pruning (#9044)" on Feb 7, 2026, 10:45 PM

tobiu Feb 7, 2026, 10:46 PM

Input from Gemini 3 Pro:

✦ Fixed critical issues in the DevRank update cycle.

Fixes

Infinite Loop for Bots: Updater.mjs now updates the tracker.json with the current timestamp even for users who return null (bots, deleted, or errors). This ensures they are not immediately re-selected by the scheduler in the next run.

Tracker Pruning: Cleanup.mjs now filters the tracker.json to remove users who have been updated but did not meet the contribution threshold (and are not whitelisted). This effectively prunes low-value users from the index, preventing the tracking file from growing indefinitely with inactive accounts.

Case Sensitivity: Storage.mjs now normalizes login keys to lowercase before updating the tracker map, preventing duplicate entries for users with different casing in different contexts.

Code committed to dev branch.

tobiu closed this issue on Feb 7, 2026, 10:46 PM