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	9293
title	Add push synchronization step for DevIndex data to pages repo
state	Closed
labels	enhancementaibuild
assignees	tobiu
createdAt	Feb 24, 2026, 5:51 PM
updatedAt	Feb 24, 2026, 5:55 PM
githubUrl	https://github.com/neomjs/neo/issues/9293
author	tobiu
commentsCount	1
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Feb 24, 2026, 5:55 PM

Add push synchronization step for DevIndex data to pages repo

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

Closed v12.0.0 enhancementaibuild

tobiu commented on Feb 24, 2026, 5:51 PM

Problem

The DevIndex data (users.jsonl) is generated and maintained within the neomjs/neo repository's automated hourly pipeline to ensure privacy and provide a single source of truth. However, the production deployment lives in the neomjs/pages repository. Currently, the data does not automatically sync to the pages repository, meaning the deployed application does not immediately reflect updates (such as opt-outs or new discovered users).

Solution

Append a new step to the .github/workflows/devindex-pipeline.yml workflow. After the pipeline finishes processing and committing the local data, it will use a Personal Access Token (PAGES_DEPLOY_PAT) to clone the neomjs/pages repository, copy the newly updated users.jsonl file into node_modules/neo.mjs/apps/devindex/resources/data/, and push the changes directly to the pages repo's main branch.

This ensures a near real-time "Push" synchronization strategy where the frontend application immediately benefits from the data factory's backend updates.

tobiu added the enhancement label on Feb 24, 2026, 5:51 PM

tobiu added the ai label on Feb 24, 2026, 5:51 PM

tobiu added the build label on Feb 24, 2026, 5:51 PM

tobiu referenced in commit 3e50e14 - "build: Add push synchronization step for DevIndex data to pages repo (#9293)" on Feb 24, 2026, 5:55 PM

tobiu assigned to @tobiu on Feb 24, 2026, 5:55 PM

tobiu Feb 24, 2026, 5:55 PM

Input from Gemini 3.1 Pro:

✦ I have successfully appended a new "Push Data to neomjs/pages" step to the devindex-pipeline.yml workflow.

As requested, it uses the standard secrets.GITHUB_TOKEN to clone the neomjs/pages repository, create the necessary nested directory structure (node_modules/neo.mjs/apps/devindex/resources/data), copy the updated users.jsonl file, and commit/push it directly to the pages repository's main branch.

Security Note: While both repositories are in the same organization, GitHub Actions scopes the default GITHUB_TOKEN to the repository running the action (i.e., neomjs/neo). Unless cross-repository access is explicitly enabled for Actions at the organization level, the push step may fail with a 403 error during the next run. If it does fail, we will need to revert to using a Personal Access Token (PAGES_DEPLOY_PAT).

The change has been committed and pushed to dev.

tobiu closed this issue on Feb 24, 2026, 5:55 PM