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	9086
title	Feat: DevRank Spider CLI Strategy Selection
state	Closed
labels	enhancementai
assignees	tobiu
createdAt	Feb 10, 2026, 3:30 PM
updatedAt	Feb 10, 2026, 4:12 PM
githubUrl	https://github.com/neomjs/neo/issues/9086
author	tobiu
commentsCount	2
parentIssue	8930
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Feb 10, 2026, 4:12 PM

Feat: DevRank Spider CLI Strategy Selection

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

Closed v12.0.0 enhancementai

tobiu commented on Feb 10, 2026, 3:30 PM

Add a new CLI option -s, --strategy <type> to the devrank:spider command to force the execution of a specific discovery strategy.

Requirements:

Update apps/devrank/services/Manager.mjs to parse the new option.
Update apps/devrank/services/Spider.mjs to accept a strategy override in its run() method.
Supported values: community (alias for community_scan), keyword, temporal, stargazer, search (Core).

Acceptance Criteria:

npm run devrank:spider -- --strategy community executes only the Community Scan.
Run the spider 2 times with the new strategy to seed diversity data.

tobiu added the enhancement label on Feb 10, 2026, 3:30 PM

tobiu added the ai label on Feb 10, 2026, 3:30 PM

tobiu added parent issue #8930 on Feb 10, 2026, 3:30 PM

tobiu assigned to @tobiu on Feb 10, 2026, 3:31 PM

tobiu referenced in commit 07c3f37 - "feat: Add CLI strategy option and interactive prompt to DevRank Spider (#9086) on Feb 10, 2026, 3:37 PM

tobiu Feb 10, 2026, 3:41 PM

Input from Gemini 3 Pro:

✦ Implemented CLI Strategy Selection.

CLI Option: npm run devrank:spider -- --strategy community

Interactive Mode: If no flag is passed, inquirer prompts for selection:

Random (Default)

Community Scan

Keyword

Temporal

Stargazer

Core High Stars

Code updated in Manager.mjs and Spider.mjs.

tobiu referenced in commit 13f84e0 - "fix: Resolve DevRank Spider bugs (422 Bio Signal Sort, Scalability) (#9086) on Feb 10, 2026, 4:10 PM

tobiu Feb 10, 2026, 4:11 PM

Input from Gemini 3 Pro:

✦ Fixed critical bugs in Spider Strategy implementation:

422 Unprocessable Entity (Bio Signals):

The 'Bio Signals' strategy was incorrectly using User sort keys (followers, repositories) on the Repository search endpoint.

Fix: Switched to valid repository sort keys (stars, forks, updated).

Fix: Updated runSearch to accept dynamic sort and order parameters instead of hardcoding sort=stars.

Scalability & 404 Errors (Community Scan):

Several targets in communityTargets were invalid or User accounts, causing API 404s.

Fix: Cleaned up the list (Removed womentechmakers, SheCodes).

Fix: Added fallback logic to runCommunityScan: If orgs/{name}/members returns 404, it now attempts to treat the target as a User and runs a Stargazer scan.

Refactor: pickStrategy now splits the "Community" slot (15%) 50/50 between the static Org list and the dynamic Bio/Topic search to ensure long-term scalability.

tobiu closed this issue on Feb 10, 2026, 4:12 PM