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	9227
title	Unify DevIndex Workflows and implement Spider backpressure
state	Closed
labels	enhancementaibuild
assignees	tobiu
createdAt	Feb 21, 2026, 3:32 PM
updatedAt	Feb 21, 2026, 3:36 PM
githubUrl	https://github.com/neomjs/neo/issues/9227
author	tobiu
commentsCount	1
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Feb 21, 2026, 3:34 PM

Unify DevIndex Workflows and implement Spider backpressure

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

Closed v12.0.0 enhancementaibuild

tobiu commented on Feb 21, 2026, 3:32 PM

The DevIndex currently uses two independent GitHub Action workflows (devindex-spider.yml and devindex-updater.yml) that run on competing 30-minute cron schedules. This leads to intermittent Git merge conflicts when both jobs attempt to modify and push tracker.json simultaneously. Furthermore, uncontrolled Spider discovery can bloat the tracker backlog.

Tasks:

Unify Workflows: Combine the Spider and Updater into a single, sequential pipeline (.github/workflows/devindex-pipeline.yml) that runs hourly. This guarantees atomic commits and zero git conflicts.
Backpressure Valve: Enhance the Spider to check the number of "pending" users (lastUpdate: null) in tracker.json. If the backlog exceeds config.spider.maxPendingUsers (e.g., 2000), the Spider should abort its discovery run to let the Updater catch up.
Restore 3x Loop: With the workflows unified and backpressure in place, the Spider can safely be restored to execute 3 discovery loops per hour instead of 1.
Cleanup: Remove the obsolete individual workflows.

tobiu added the epic label on Feb 21, 2026, 3:32 PM

tobiu added the ai label on Feb 21, 2026, 3:32 PM

tobiu added the build label on Feb 21, 2026, 3:32 PM

tobiu referenced in commit d106ed9 - "build(devindex): Unify GH Actions into single pipeline and add Spider backpressure (#9227)" on Feb 21, 2026, 3:33 PM

tobiu assigned to @tobiu on Feb 21, 2026, 3:34 PM

tobiu Feb 21, 2026, 3:34 PM

Input from Gemini 3 Pro:

✦ I have implemented the Unified Pipeline and Spider Backpressure as requested.

Created .github/workflows/devindex-pipeline.yml to replace the two independent cron jobs, orchestrating the 3x Spider Loop followed immediately by the Updater within a single, sequential job.

Removed devindex-spider.yml and devindex-updater.yml to eliminate Git merge conflicts and double-running.

Modified apps/devindex/services/config.mjs to add maxPendingUsers: 2000 to the spider configuration.

Modified apps/devindex/services/Spider.mjs run() method to check the number of users with lastUpdate: null. If this backlog equals or exceeds the maxPendingUsers cap, the Spider now immediately aborts its run, forcing it to sleep and letting the Updater consume the existing queue.

These changes have been committed, rebased over the latest remote background updates, and pushed to dev. Closing issue.

tobiu closed this issue on Feb 21, 2026, 3:34 PM

tobiu removed the epic label on Feb 21, 2026, 3:36 PM

tobiu added the enhancement label on Feb 21, 2026, 3:36 PM