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	9237
title	Process Issue Templates for DevIndex Opt-In
state	Closed
labels	enhancementai
assignees	tobiu
createdAt	Feb 22, 2026, 12:29 AM
updatedAt	Feb 22, 2026, 12:42 AM
githubUrl	https://github.com/neomjs/neo/issues/9237
author	tobiu
commentsCount	1
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Feb 22, 2026, 12:42 AM

Process Issue Templates for DevIndex Opt-In

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

Closed v12.0.0 enhancementai

tobiu commented on Feb 22, 2026, 12:29 AM

Description

Implement the automated pipeline to process the two new issue templates in the neomjs/devindex-opt-in repository: "DevIndex Opt-In (Myself)" and "DevIndex Opt-In (Nominate Others)".

Requirements

Fetch Issues: Query the GitHub GraphQL API to fetch open issues with the devindex-opt-in label.
Differentiate Request Types: Parse the issue title to determine if it's a "Self" request or an "Others" nomination.
Process "Self" Requests (Identity Verified):
- Extract the issue author's username.
- Blocklist Reversal: Since the identity is verified, remove the user from the blocklist if they are on it.
- Add to tracker.json (if not already tracked/indexed).
Process "Nominate Others" Requests (Unverified Identity):
- Extract the list of usernames from the issue body.
- Validate that the usernames exist on GitHub (e.g., via a quick GraphQL user(login: "...") check).
- NO Blocklist Reversal: Crucially, do NOT remove these users from the blocklist. A third party cannot override a personal opt-out.
- Add valid, non-blocklisted users to tracker.json (if not already tracked/indexed).
Issue Management: Add an automated comment to the issue summarizing the actions taken and close the issue.

tobiu added the enhancement label on Feb 22, 2026, 12:29 AM

tobiu added the ai label on Feb 22, 2026, 12:29 AM

tobiu assigned to @tobiu on Feb 22, 2026, 12:29 AM

tobiu referenced in commit 531ea51 - "feat: Process Issue Templates for DevIndex Opt-In (#9237)" on Feb 22, 2026, 12:41 AM

tobiu Feb 22, 2026, 12:41 AM

Input from Gemini 3 Pro:

✦ I have implemented the logic to process the issue templates for Opt-In requests in the OptIn.mjs service.

"Self" Requests: Handled accurately by extracting the author's login, adding them to the tracker, and explicitly removing them from the blocklist.

"Nominate Others" Requests:

Uses improved regex parsing to extract usernames from the issue body, filtering out markdown list artifacts.

Validates each username against the GitHub REST API (users/${uname}).

Appends valid usernames to the tracker without removing them from the blocklist.

Constructs meaningful, dynamic comments that explicitly list which users were successfully added and which failed validation.

Closing Actions: Issues are automatically commented on and closed after processing.

This feature is now fully operational.

tobiu closed this issue on Feb 22, 2026, 12:42 AM

tobiu referenced in commit 26878fc - "feat: Add detailed comment status for DevIndex Opt-In (#9237)" on Feb 22, 2026, 12:47 AM

tobiu referenced in commit 58be928 - "feat: Add self-opt-in hint for blocked users (#9237)" on Feb 22, 2026, 12:49 AM