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	9235
title	DevIndex: Adjust Meritocracy Filter to exclude allowlisted users from the maxUsers cap
state	Closed
labels	enhancementai
assignees	tobiu
createdAt	Feb 21, 2026, 11:35 PM
updatedAt	Feb 21, 2026, 11:43 PM
githubUrl	https://github.com/neomjs/neo/issues/9235
author	tobiu
commentsCount	1
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Feb 21, 2026, 11:43 PM

DevIndex: Adjust Meritocracy Filter to exclude allowlisted users from the maxUsers cap

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

Closed v12.0.0 enhancementai

tobiu commented on Feb 21, 2026, 11:35 PM

Description

Currently, the updateUsers method in Storage.mjs strictly slices the users.jsonl array at config.github.maxUsers. This creates an unfair scenario where manually allowlisted users (e.g., conference speakers who haven't met the organic threshold) consume slots that belong to organic, high-contributing developers.

Requirements

Update apps/devindex/services/Storage.mjs.
Inside updateUsers(), fetch the current allowlist size.
Calculate the effectiveMax as config.github.maxUsers + allowlist.size.
Use this effectiveMax when slicing the array and calculating pruning logic.
This ensures 50,000 organic slots are always protected, plus however many manual allowlist entries exist.

tobiu added the enhancement label on Feb 21, 2026, 11:35 PM

tobiu added the ai label on Feb 21, 2026, 11:35 PM

tobiu referenced in commit fecd5b5 - "fix(devindex): Adjust Meritocracy Filter to exclude allowlisted users from maxUsers cap (#9235)" on Feb 21, 2026, 11:41 PM

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

tobiu Feb 21, 2026, 11:43 PM

Input from Gemini 3 Pro:

✦ I have implemented the fix for the Meritocracy Filter.

Changes Made:

apps/devindex/services/Storage.mjs: Updated the updateUsers method to calculate an effectiveMax.

Logic: The script now dynamically fetches the size of the allowlist and adds it to config.github.maxUsers. The array is sliced at this new effectiveMax boundary.

Knowledge Base Enhancement: Added a detailed, intent-driven comment directly into the source code explaining exactly why this calculation exists (to protect organic slots from being consumed by manual overrides).

This ensures the platform remains fair and meritocratic, even when manual exceptions are granted! Changes have been pushed to dev. Closing the ticket.

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