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	9455
title	Integrate RPC API into Pipeline Architecture (Connection.Rpc)
state	Closed
labels	enhancementaiarchitecturecore
assignees	tobiu
createdAt	Mar 12, 2026, 10:03 PM
updatedAt	Mar 25, 2026, 11:34 AM
githubUrl	https://github.com/neomjs/neo/issues/9455
author	tobiu
commentsCount	1
parentIssue	9449
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Mar 25, 2026, 11:34 AM

Integrate RPC API into Pipeline Architecture (Connection.Rpc)

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

Closed v12.1.0 enhancementaiarchitecturecore

tobiu commented on Mar 12, 2026, 10:03 PM

Goal

Unify the standalone RPC API with the Data Pipeline architecture. Allow Neo.data.Store to use RPC as a transport, and conversely, allow standalone RPC calls to utilize Parsers and Normalizers.

Context

Currently, the RPC API bypasses all parsing and normalization. If a Store uses an api config, it calls generated proxy functions that return raw JSON directly from the Data Worker to the App Worker Store. This prevents us from using powerful Normalizers (like Tree) with RPC data.

We need to create a "Merged Universe" where data shaping is transport-agnostic and available everywhere.

Acceptance Criteria

1. Store to RPC (Connection.Rpc)

Create Neo.data.connection.Rpc extending connection.Base.
Instead of a url config, it accepts an api config (e.g., 'MyApp.backend.ColorService').
Its read() method acts as an adapter: it invokes the underlying RPC proxy method within the Data Worker.
The raw JSON response is returned to the Data Worker's Pipeline, which pipes it through the Parser and Normalizer before sending the final data back to the App Worker Store.

2. RPC to Pipeline (The Merged Universe)

Enhance Neo.remotes.Api to inspect remotes-api.json configurations.
If an RPC endpoint (method or stream) defines a parser or normalizer config, the generateRemote proxy function must be wrapped.
When an App Worker ViewController calls this RPC proxy, the Data Worker must automatically pipe the backend's raw response through the specified Pipeline components before fulfilling the Promise (or triggering the callback) back in the App Worker.
This ensures UI components only ever receive perfectly shaped, predictable data structures, regardless of backend formatting.

tobiu added the enhancement label on Mar 12, 2026, 10:03 PM

tobiu added the ai label on Mar 12, 2026, 10:03 PM

tobiu added the architecture label on Mar 12, 2026, 10:03 PM

tobiu added the core label on Mar 12, 2026, 10:03 PM

tobiu cross-referenced by #9449 on Mar 12, 2026, 10:03 PM

tobiu added parent issue #9449 on Mar 12, 2026, 10:04 PM

tobiu assigned to @tobiu on Mar 12, 2026, 10:04 PM

tobiu referenced in commit 2a9910d - "feat: Integrate RPC API into Pipeline Architecture (Connection.Rpc) (#9455)" on Mar 25, 2026, 11:29 AM

tobiu Mar 25, 2026, 11:30 AM

Input from Gemini 3.1 Pro:

✦ I have successfully implemented and committed the fix for this issue.

Actions Taken:

Created src/data/connection/Rpc.mjs to act as an adapter between the new Pipeline architecture and the existing Neo.manager.rpc.Message router.

Added a generic execute() method to Neo.data.Pipeline to handle arbitrary RPC proxy methods.

Refactored Neo.remotes.Api#register to analyze remotes-api.json endpoint configs. If an endpoint specifies parser or normalizer configurations, it now dynamically instantiates a Pipeline in the App Worker (which in turn uses IPC to spawn the remote execution counterpart in the Data Worker). The generated proxy function is cleanly wrapped, sending the raw Data Worker response through the shaping pipeline before fulfilling the promise in the UI.

The "Merged Universe" is now foundational; data shaping is completely agnostic to whether the transport is Fetch, WebSocket streams, or an RPC proxy.

tobiu closed this issue on Mar 25, 2026, 11:34 AM