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	9043
title	Enhancement: DevRank Updater Smart Scheduling & Logs
state	Closed
labels	enhancementai
assignees	tobiu
createdAt	Feb 7, 2026, 10:29 PM
updatedAt	Feb 7, 2026, 10:33 PM
githubUrl	https://github.com/neomjs/neo/issues/9043
author	tobiu
commentsCount	1
parentIssue	8930
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Feb 7, 2026, 10:33 PM

Enhancement: DevRank Updater Smart Scheduling & Logs

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

Closed v12.0.0 enhancementai

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

Enhance the DevRank Updater workflow to be more efficient and informative.

Goals:

Skip Same-Day Updates: Ensure that users who have already been updated "today" (local calendar day) are excluded from the update batch, preventing redundant API calls.
Summary Logs: Provide clear feedback at the end of the run:
- How many users were actually updated.
- How many users are pending an update (Backlog size).

Changes:

Refactor apps/devrank/services/Manager.mjs:
- In runUpdate:
  - Calculate today (YYYY-MM-DD).
  - Filter out users where lastUpdate starts with today.
  - Calculate backlogSize (count of remaining stale users).
  - Pass the filtered list to Updater.
  - Log the backlog size.
Refactor apps/devrank/services/Updater.mjs:
- Track successful updates count in processBatch.
- Add a final summary log.

tobiu added the enhancement label on Feb 7, 2026, 10:29 PM

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

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

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

tobiu referenced in commit fa4da6d - "enhancement: DevRank Updater Smart Scheduling & Logs (#9043)" on Feb 7, 2026, 10:32 PM

tobiu Feb 7, 2026, 10:33 PM

Input from Gemini 3 Pro:

✦ Enhanced the DevRank Updater with smart scheduling and summary logs.

Changes

Smart Scheduling: Manager.mjs now calculates today and filters out users whose lastUpdate timestamp starts with today's date. This prevents redundant API calls for users already updated in the current calendar day.

Summary Logs: Updater.mjs and Manager.mjs now output a clear summary at the end of the run, including the count of successfully updated users and the remaining backlog size.

Example Output
[Manager] Backlog size: 543 users (pending update today).
...
--------------------------------------------------
[Updater] Run Complete.
[Updater] Successfully Updated: 100
[Updater] Remaining Backlog: 443
--------------------------------------------------
Code committed to dev branch.

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