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	9502
title	Migrate existing Stores to the new Pipeline architecture
state	Closed
labels	enhancementairefactoringarchitecturecore
assignees	tobiu
createdAt	Mar 17, 2026, 6:46 PM
updatedAt	Mar 25, 2026, 4:28 PM
githubUrl	https://github.com/neomjs/neo/issues/9502
author	tobiu
commentsCount	3
parentIssue	9449
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Mar 25, 2026, 4:25 PM

Migrate existing Stores to the new Pipeline architecture

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

Closed v12.1.0 enhancementairefactoringarchitecturecore

tobiu commented on Mar 17, 2026, 6:46 PM

Goal

Identify and migrate all existing Neo.data.Store instances in the apps/ and examples/ directories that directly use the api or url configs to utilize the new Neo.data.Pipeline architecture.

Context

With the introduction of the Pipeline cornerstone (#9451), the Store now delegates data fetching and shaping to its pipeline config. To avoid regressions and maintain a clean architecture, we must transition existing stores to this new model.

Acceptance Criteria

Search apps/ and examples/ for store definitions using api: or url:.
Refactor these stores to use the pipeline config.
Ensure Connection.Rpc or Connection.Fetch is used within the pipeline as appropriate.
Verify that examples and apps still function correctly after the migration.

tobiu assigned to @tobiu on Mar 17, 2026, 6:46 PM

tobiu added the enhancement label on Mar 17, 2026, 6:46 PM

tobiu added the ai label on Mar 17, 2026, 6:46 PM

tobiu added the refactoring label on Mar 17, 2026, 6:46 PM

tobiu added the architecture label on Mar 17, 2026, 6:46 PM

tobiu added the core label on Mar 17, 2026, 6:46 PM

tobiu added parent issue #9449 on Mar 17, 2026, 6:46 PM

tobiu cross-referenced by #9449 on Mar 17, 2026, 6:47 PM

tobiu referenced in commit 327d31e - "refactor(data): remove Pipeline legacy bridge and migrate DevIndex to explicit pipeline (#9502) on Mar 24, 2026, 8:07 PM

tobiu Mar 24, 2026, 8:07 PM

Input from Gemini 3.1 Pro:

✦ I have refactored the DevIndex.store.Contributors to explicitly configure its pipeline and explicitly import its Connection and Parser classes.

This allowed me to remove the "magical" legacy bridge from src/data/Store.mjs entirely. The Store no longer statically imports connections to try and guess the developer's intent.

By demanding explicit configuration for advanced pipeline setups, we eliminate the need for synchronous ClassSystemUtil instantiation tricks and ensure the App Worker's dependency graph remains lean and predictable. This is a crucial first step for the #9502 migration.

tobiu cross-referenced by #9550 on Mar 25, 2026, 4:23 PM

tobiu Mar 25, 2026, 4:25 PM

superseded by #9550

tobiu closed this issue on Mar 25, 2026, 4:25 PM

tobiu Mar 25, 2026, 4:28 PM

Input from Gemini 3.1 Pro:

✦ I have implemented a reactive legacy bridge in Store.mjs as part of the #9502 refactoring efforts.

The new logic in beforeSetPipeline automatically creates a connection-xhr pipeline if a url is provided without a pipeline or api. This ensures backward compatibility for simple stores while keeping the App Worker's dependency graph lean via dynamic imports.

The load() and autoLoad processes now correctly await the bridge initialization to prevent race conditions. The portal app's store-driven views are now functioning correctly.

Detailed changes can be found in #9550.