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	9543
title	Store Pipeline Instantiation and Legacy Parser Compatibility
state	Closed
labels	enhancementaiarchitecturecore
assignees	tobiu
createdAt	Mar 24, 2026, 5:07 PM
updatedAt	Mar 24, 2026, 7:39 PM
githubUrl	https://github.com/neomjs/neo/issues/9543
author	tobiu
commentsCount	1
parentIssue	9449
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Mar 24, 2026, 7:39 PM

Store Pipeline Instantiation and Legacy Parser Compatibility

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

Closed v12.1.0 enhancementaiarchitecturecore

tobiu commented on Mar 24, 2026, 5:07 PM

Goal

Address the architectural friction introduced in #9452 when migrating existing Stores to the new Pipeline architecture, specifically resolving the class instantiation issues within Neo.data.Store.

Context

During the completion of #9452 (Connection Foundation and Parser Refactoring), we successfully separated network logic from parsers. However, applying this to live stores (like apps/devindex/store/Contributors.mjs) revealed two major bottlenecks:

Pipeline Instantiation Failure (Store.mjs): The beforeSetPipeline method in Neo.data.Store currently attempts to use ClassSystemUtil.beforeSetInstance(value, null, ...). Because it passes null as the default class, supplying a raw pipeline: { connection: {...}, parser: {...} } config object fails to instantiate a Neo.data.Pipeline class, crashing with "missing className or module property".
Dynamic Connection Imports: If a Store requires a Connection in the App Worker (e.g., connection.Stream), attempting to use dynamic imports module: () => import(...) inside the Store's pipeline config fails synchronously during ClassSystemUtil instantiation.
Legacy Fallback: Neo.data.Store still contains many references to store.parser and store.url.

Acceptance Criteria

Fix Pipeline Instantiation: Update src/data/Store.mjs to correctly resolve and instantiate Neo.data.Pipeline in beforeSetPipeline().
Address Circular Dependencies: Ensure importing Pipeline into Store (or vice versa) does not create unresolved circular dependencies during framework boot.
Bridge Legacy Configs: Implement a temporary bridge in Store.mjs that detects legacy parser: {} and url: '' configs and automatically wraps them into a pipeline: {} config before beforeSetPipeline executes.
Fix DevIndex Tests: Ensure test/playwright/unit/app/devindex/StoreFilterProfile.spec.mjs and test/playwright/unit/data/StoreParser.spec.mjs pass cleanly with the new architecture.

Next Steps

This issue must be resolved to stabilize the codebase before proceeding with IPC routing (#9453).

tobiu added the enhancement label on Mar 24, 2026, 5:07 PM

tobiu added the ai label on Mar 24, 2026, 5:07 PM

tobiu added the architecture label on Mar 24, 2026, 5:07 PM

tobiu added the core label on Mar 24, 2026, 5:07 PM

tobiu added parent issue #9449 on Mar 24, 2026, 5:08 PM

tobiu assigned to @tobiu on Mar 24, 2026, 5:10 PM

tobiu referenced in commit 618c3f3 - "fix(data): fix Pipeline instantiation and dynamic import issues inside Store (#9543) on Mar 24, 2026, 7:38 PM

tobiu Mar 24, 2026, 7:39 PM

Input from Gemini 3.1 Pro:

✦ I have addressed the pipeline instantiation and legacy parser compatibility issues within Store.mjs.

Key Changes:

Legacy Bridge: Implemented an override for mergeConfig() in Store.mjs that intercepts legacy parser and url configs. It dynamically maps these into the new pipeline: { connection: {...}, parser: {...} } format before the beforeSetPipeline lifecycle hook executes.

Static Imports: Bypassed the synchronous ClassSystemUtil instantiation issue for dynamic imports by explicitly importing ConnectionFetch and ConnectionStream within Store.mjs. This guarantees their ntypes (connection-fetch, connection-stream) are registered in the main worker threads and can be reliably resolved by ClassSystemUtil without needing dynamic module: () => import(...).

Pipeline Event Propagation: Updated Pipeline.mjs to explicitly relay data and progress events from its internal parser to the Pipeline instance itself. This ensures that progressive loading (streaming) correctly bubbles up to the Store's listeners.

Unit Tests: Updated test/playwright/unit/data/StoreParser.spec.mjs to reflect the new nested pipeline object structure. All unit tests, including StoreFilterProfile.spec.mjs, now pass successfully.

This stabilizes the Store architecture and clears the path for implementing IPC routing. I will now close this sub-issue.

tobiu closed this issue on Mar 24, 2026, 7:39 PM