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	9564
title	Finalize Data Pipeline Push Integration & UI Reactivity
state	Closed
labels	enhancementaiarchitecturecore
assignees	tobiu
createdAt	Mar 26, 2026, 5:13 PM
updatedAt	Mar 26, 2026, 6:12 PM
githubUrl	https://github.com/neomjs/neo/issues/9564
author	tobiu
commentsCount	1
parentIssue	9449
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Mar 26, 2026, 6:12 PM

Finalize Data Pipeline Push Integration & UI Reactivity

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

Closed v12.1.0 enhancementaiarchitecturecore

tobiu commented on Mar 26, 2026, 5:13 PM

Goal

Connect the lower-level WebSocket/Stream RPC mechanisms to the Store so that unsolicited server pushes surgically update UI components via record.set().

Context

In issue #9454, we implemented the plumbing for Progressive Hydration (WebSocket persistent subscriptions, RPC routing, IPC forwarding). However, we missed the final integration step: The Store itself is not listening for these pushes, and the pipeline abstraction lacks a dedicated push or update event to notify the store.

If a server pushes { id: 123, status: 'done' } right now, it traverses the worker boundary but dies in the App Worker because the Store is only listening to load and progress (for chunking), not unsolicited push events.

Acceptance Criteria

Connection Event Emission:
- src/data/connection/WebSocket.mjs (and potentially Rpc) must fire a push event when unsolicited data arrives, rather than just executing hardcoded callbacks.
Pipeline Event Bridging:
- src/data/Pipeline.mjs must relay push events from its connection to the outside world.
- It must run pushed data through the parser and normalizer before emitting pipeline.fire('push', shapedData).
- It must correctly handle IPC forwarding for pushes when workerExecution: 'data'.
Store Integration (record.set()):
- src/data/Store.mjs must listen to the push event on its pipeline.
- Implement onPipelinePush(data). This method must locate the existing record via its primary key and call record.set(data) to trigger a surgical VDOM update without reloading the entire collection.
Unit Testing (test/playwright/unit/data/):
- Create PipelinePush.spec.mjs to verify event bubbling, shaping, and IPC forwarding using mock connections.
- Create StorePush.spec.mjs to verify that a Store correctly interprets pipeline pushes and applies surgical updates via record.set(), triggering a recordChange event.

tobiu added the enhancement label on Mar 26, 2026, 5:13 PM

tobiu added the ai label on Mar 26, 2026, 5:13 PM

tobiu added the architecture label on Mar 26, 2026, 5:13 PM

tobiu added the core label on Mar 26, 2026, 5:13 PM

tobiu added parent issue #9449 on Mar 26, 2026, 5:14 PM

tobiu assigned to @tobiu on Mar 26, 2026, 5:14 PM

tobiu referenced in commit 53d3459 - "feat: Finalize Data Pipeline Push Integration & UI Reactivity (#9564)" on Mar 26, 2026, 6:10 PM

tobiu Mar 26, 2026, 6:11 PM

Input from Gemini 3.1 Pro:

✦ I have implemented the final integration for the push-based data pipeline.

Summary of Changes:

src/data/connection/Base.mjs: Made the base connection observable so that all connection types (including WebSocket) can emit custom events like push.

src/data/connection/WebSocket.mjs: Now fires a push event when unsolicited data (Progressive Hydration) arrives without a matching callback or Promise mId.

src/data/Pipeline.mjs: Implemented onConnectionPush to relay the push event from its underlying connection.

It passes the pushed data through the parser and normalizer.

If running in the Data Worker, it forwards the shaped data via IPC to the App Worker Pipeline.

src/worker/App.mjs: Added onPipelinePush(msg) to catch the IPC forward and re-emit the push event on the correct proxy pipeline instance inside the App Worker.

src/data/Store.mjs: The Store now listens to push events from its configured pipeline.

Added onPipelinePush(data): It looks up the record by its primary key, and if it exists, it executes record.set(data). This completes the flow and triggers the surgical VDOM update without reloading the grid or collection.

Unit Tests: Added PipelinePush.spec.mjs and StorePush.spec.mjs to rigorously verify the event bubbling and the surgical record.set() updates using mock connections.

These changes have been committed and pushed to the repository. I will now close this issue.

tobiu closed this issue on Mar 26, 2026, 6:12 PM