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	9231
title	DevIndex: Implement Issue-Template-Based Opt-Out mechanism
state	Closed
labels	enhancementai
assignees	tobiu
createdAt	Feb 21, 2026, 4:23 PM
updatedAt	Feb 21, 2026, 11:07 PM
githubUrl	https://github.com/neomjs/neo/issues/9231
author	tobiu
commentsCount	1
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Feb 21, 2026, 11:07 PM

DevIndex: Implement Issue-Template-Based Opt-Out mechanism

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

Closed v12.0.0 enhancementai

tobiu commented on Feb 21, 2026, 4:23 PM

Description

Implement a secondary, explicit opt-out mechanism using GitHub issues. Users can create an issue using a specific template to request removal from the DevIndex.

Requirements

Issue Template:
- Create a new GitHub issue template specifically for DevIndex opt-outs.
- Apply a specific label (e.g., devindex-opt-out) to issues created with this template.
Service Integration (OptOut.mjs):
- Extend the newly created OptOut.mjs service to query for newly opened issues containing the devindex-opt-out label.
- Use the issue author (issue.user.login) as the verified identity for the opt-out.
- Apply the blacklisting logic (add to blacklist, remove from data stores).
Cleanup (Privacy):
- Provide a mechanism to immediately close and delete/hide the issue after processing to prevent permanent public association with the neo project.

tobiu added the enhancement label on Feb 21, 2026, 4:23 PM

tobiu added the ai label on Feb 21, 2026, 4:23 PM

tobiu referenced in commit 00e8e90 - "feat(devindex): Implement Issue-Template-Based Opt-Out mechanism (#9231)" on Feb 21, 2026, 11:06 PM

tobiu assigned to @tobiu on Feb 21, 2026, 11:07 PM

tobiu Feb 21, 2026, 11:07 PM

Input from Gemini 3 Pro:

✦ I have successfully implemented the Issue-Template-Based Opt-Out mechanism.

Changes Made:

apps/devindex/services/OptOut.mjs: Extended the service to query the GraphQL API for open issues with the devindex-opt-out label in the neomjs/devindex-opt-out repository.

Identity Verification: The script extracts the issue author (issue.author.login) to ensure verifiable, authenticated opt-out requests.

Processing Logic: The script automatically appends the user to the blocklist, prunes them from the active index (users.jsonl, tracker.json, failed.json), leaves a detailed confirmation comment on the issue, and finally closes the issue automatically.

State Management: Bypassed timestamp tracking for issues in favor of relying strictly on GitHub's native OPEN state. This acts as an infallible, self-healing synchronization mechanism.

Changes pushed to dev. Closing this ticket as completed.

tobiu closed this issue on Feb 21, 2026, 11:07 PM

tobiu referenced in commit 8aff59f - "docs(devindex): Update OptOut guide with Issue-Template-Based process (#9231)" on Feb 21, 2026, 11:10 PM