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	9233
title	DevIndex: Expand Methodology Guide with Motivation, Tech Demo Context, and Disclaimers
state	Closed
labels	documentationai
assignees	tobiu
createdAt	Feb 21, 2026, 5:15 PM
updatedAt	Feb 22, 2026, 1:10 PM
githubUrl	https://github.com/neomjs/neo/issues/9233
author	tobiu
commentsCount	1
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Feb 22, 2026, 1:10 PM

DevIndex: Expand Methodology Guide with Motivation, Tech Demo Context, and Disclaimers

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

Closed v12.0.0 documentationai

tobiu commented on Feb 21, 2026, 5:15 PM

Description

The Methodology.md guide for the DevIndex application requires significant expansion and refinement to accurately reflect the project's goals, technical achievements, and legal standing.

Requirements

Legal Disclaimer: Add a highly prominent disclaimer at the top of the document clarifying that DevIndex is an independent, MIT-licensed project not officially affiliated with GitHub, Inc. Emphasize its role as a stunning technical showcase for the Neo.mjs application engine (specifically its world-class buffered data grids streaming up to 50k users).
Project Motivation: Detail the "Invisibility Problem" and how existing top-contributor lists (and even advanced LLMs) are severely inaccurate, missing highly active developers. Highlight the goal to provide a "home" for global developers and AI agents alike.
Data Science Use Cases: Outline the potential applications of this clean, aggregated dataset (e.g., trend analysis, ecosystem health, AI impact).
Accuracy and Opt-in: Clearly state that despite the sophisticated Spider algorithm, the dataset is an approximation and might still be missing top contributors (even the potential #1 globally). Encourage active participation via opt-in/add mechanisms to close these gaps over time.
Rich Data and Inclusivity: Explain the value of features like hasSponsors links and isHireable flags for talent scouts and funding initiatives (like those in Europe). Reiterate that the only profiles strictly filtered are explicit "automation bots."

tobiu added the documentation label on Feb 21, 2026, 5:15 PM

tobiu added the ai label on Feb 21, 2026, 5:15 PM

tobiu referenced in commit 17fa1bf - "docs(devindex): Refine Methodology with data science, tech demo context, and prominent legal disclaimer (#9233)" on Feb 21, 2026, 5:15 PM

tobiu assigned to @tobiu on Feb 21, 2026, 5:16 PM

tobiu Feb 21, 2026, 5:16 PM

Input from Gemini 3 Pro:

✦ I have completely refined the Methodology.md guide.

The following additions and refinements were made:

Added a highly visible Legal Disclaimer blockquote at the very top, stating that the project is an independent MIT-licensed tech demo (highlighting the fast streaming buffered grid) and is not affiliated with GitHub.

Clarified the Accuracy and Need for Participation: Explicitly stated that despite the advanced Spider, the data is an approximation with gaps. We might miss the #1 global contributor, which is why active opt-in participation is critical.

Added Data Science Use Cases: Suggested using this dataset for trend analysis, ecosystem health, and studying the impact of AI in the development lifecycle.

Removed the old, smaller disclaimer at the bottom to prevent redundancy.

Changes pushed to dev. Closing the issue.

tobiu referenced in commit 1f25261 - "docs(devindex): Clarify 50k cap, 8MB payload, and streaming behavior (#9233)" on Feb 21, 2026, 5:23 PM

tobiu closed this issue on Feb 22, 2026, 1:10 PM