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	9420
title	Migrate Data Pipeline to Connection -> Parser -> Normalizer flow
state	Closed
labels	enhancementairefactoringarchitecturecore
assignees	tobiu
createdAt	Mar 9, 2026, 4:46 PM
updatedAt	Mar 12, 2026, 4:37 PM
githubUrl	https://github.com/neomjs/neo/issues/9420
author	tobiu
commentsCount	1
parentIssue	9449
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Mar 12, 2026, 4:37 PM

Migrate Data Pipeline to Connection -> Parser -> Normalizer flow

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

Closed v12.1.0 enhancementairefactoringarchitecturecore

tobiu commented on Mar 9, 2026, 4:46 PM

Goal

Wire the new Parser/Normalizer architecture through the entire data pipeline, ensuring the Data Worker performs all transformations before sending data back to the App Worker.

Context

With Normalizers defined and the Data Worker capable of dynamically loading them via RMA, the execution flow must be updated to shift heavy lifting out of the App Worker.

Acceptance Criteria

Deprecate/Rename Neo.data.proxy.* namespace in favor of Neo.data.parser.* (e.g., Neo.data.parser.Stream).
Store.load() calls should pass the parser and normalizer module paths down to the Connection via the worker bridge.
Neo.data.connection.Fetch and Neo.data.connection.Xhr (running in the Data Worker) must intercept the response, instantiate the requested Parser, pass the JS object to the requested Normalizer, and postMessage the final flattened data back to the App Worker.

tobiu added the enhancement label on Mar 9, 2026, 4:46 PM

tobiu added the ai label on Mar 9, 2026, 4:46 PM

tobiu added the refactoring label on Mar 9, 2026, 4:46 PM

tobiu added the architecture label on Mar 9, 2026, 4:46 PM

tobiu added the core label on Mar 9, 2026, 4:46 PM

tobiu added parent issue #9404 on Mar 9, 2026, 4:46 PM

tobiu assigned to @tobiu on Mar 9, 2026, 4:47 PM

tobiu cross-referenced by #9449 on Mar 12, 2026, 3:20 PM

tobiu removed parent issue #9404 on Mar 12, 2026, 3:21 PM

tobiu added parent issue #9449 on Mar 12, 2026, 3:21 PM

tobiu referenced in commit 5261e90 - "feat: Migrate Data Pipeline to Connection -> Parser -> Normalizer flow (#9420) on Mar 12, 2026, 4:36 PM

tobiu Mar 12, 2026, 4:37 PM

Input from Gemini 3.1 Pro:

✦ I have completed the migration of the Data Pipeline to the Connection -> Parser -> Normalizer flow.

Changes Made:

Renamed Proxy to Parser: Moved src/data/proxy/ to src/data/parser/.

Refactored Store and TreeStore: Changed all instances of proxy and proxy_ configs to parser and parser_. The .load() flow now routes through the parser.

Updated Apps & Tests: Updated the devindex app to use parser instead of proxy for its Stream pipeline. Renamed and updated the Playwright unit tests to validate StoreParser instead of StoreProxy. All 331 unit tests continue to pass.

Committed and pushed under #9420.

tobiu closed this issue on Mar 12, 2026, 4:37 PM