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	9290
title	Refactor DevIndex data deployment strategy to prevent huge resource duplication
state	Closed
labels	enhancementaibuild
assignees	tobiu
createdAt	Feb 24, 2026, 4:54 PM
updatedAt	Feb 24, 2026, 4:57 PM
githubUrl	https://github.com/neomjs/neo/issues/9290
author	tobiu
commentsCount	1
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Feb 24, 2026, 4:57 PM

Refactor DevIndex data deployment strategy to prevent huge resource duplication

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

Closed v12.0.0 enhancementaibuild

tobiu commented on Feb 24, 2026, 4:54 PM

Problem

The apps/devindex/resources folder contains heavy data files, notably the users.jsonl file which is currently 22MB. When building the project for dist/development and dist/production environments, the build scripts (buildScripts/webpack/... and buildScripts/build/esmodules.mjs) blindly copy everything in the resources directory.

This leads to significant, unnecessary duplication of heavy data files in the deployment artifacts. Furthermore, the backend data factory needs a single source of truth (the dev branch data) to act upon.

Solution

Move the data files (*.json, *.jsonl) within apps/devindex/resources into a dedicated data/ subdirectory (apps/devindex/resources/data).
Update the backend data factory config (apps/devindex/services/config.mjs) to point to the new data/ paths.
Update the Contributors.mjs store proxy URL to fetch data from Neo.config.basePath + 'apps/devindex/resources/data/users.jsonl'. This ensures that dist environments correctly resolve the path back to the original source folder, enabling them to pull data from the dev environment as the single source of truth.
Modify the resource copying logic in the build scripts (webpack.config.appworker.mjs for dev and prod, and esmodules.mjs) to explicitly remove the data directory from apps/devindex/resources after the initial copy, preventing the heavy files from being deployed to dist/.

tobiu added the enhancement label on Feb 24, 2026, 4:54 PM

tobiu added the ai label on Feb 24, 2026, 4:54 PM

tobiu added the build label on Feb 24, 2026, 4:54 PM

tobiu referenced in commit 04a30f4 - "build: Refactor DevIndex data deployment strategy (#9290)" on Feb 24, 2026, 4:55 PM

tobiu assigned to @tobiu on Feb 24, 2026, 4:56 PM

tobiu Feb 24, 2026, 4:56 PM

Input from Gemini 3.1 Pro:

✦ I have successfully moved the *.json and *.jsonl files from apps/devindex/resources to apps/devindex/resources/data. The config.mjs has been updated to point to the new paths, and the Contributors.mjs store now fetches the users.jsonl data correctly using Neo.config.basePath.

I have also updated the build scripts (buildScripts/webpack/production/webpack.config.appworker.mjs, buildScripts/webpack/development/webpack.config.appworker.mjs, and buildScripts/build/esmodules.mjs) with an explicit exception for the DevIndex app. The scripts now remove the data directory from the copied resources folder, preventing the 22MB users.jsonl and other data files from being duplicated in the dist builds.

The changes have been pushed to the dev branch.

tobiu closed this issue on Feb 24, 2026, 4:57 PM