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	9452
title	Connection Foundation and Parser Refactoring
state	Closed
labels	enhancementaiarchitecturecore
assignees	tobiu
createdAt	Mar 12, 2026, 7:22 PM
updatedAt	Mar 24, 2026, 4:06 PM
githubUrl	https://github.com/neomjs/neo/issues/9452
author	tobiu
commentsCount	1
parentIssue	9449
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Mar 24, 2026, 4:06 PM

Connection Foundation and Parser Refactoring

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

Closed v12.1.0 enhancementaiarchitecturecore

tobiu commented on Mar 12, 2026, 7:22 PM

Goal

Establish the Neo.data.connection.Base hierarchy and fix the abstraction leak in Neo.data.parser.Stream by extracting its network transport logic.

Context

A Parser should strictly focus on deserialization and shaping data (e.g., converting a text stream into JSON records). Currently, Neo.data.parser.Stream has fetch() and AbortController logic hardcoded into its read() method. This makes it a Connection in disguise and violates the single responsibility principle.

Acceptance Criteria

Create src/data/connection/Base.mjs.
Refactor Neo.data.connection.Fetch and Xhr to extend this new Base class.
Create a new Connection (e.g., connection.Stream or enhance connection.Fetch) that handles the fetch() request and returns the ReadableStream.
Refactor Neo.data.parser.Stream: Remove the fetch() call. The parser should now accept the ReadableStream provided by the Connection, process the NDJSON/JSONL chunks, and yield records.
Ensure the Pipeline class correctly routes the output of the Connection into the Parser.

tobiu added the enhancement label on Mar 12, 2026, 7:22 PM

tobiu added the ai label on Mar 12, 2026, 7:22 PM

tobiu added the architecture label on Mar 12, 2026, 7:22 PM

tobiu added the core label on Mar 12, 2026, 7:22 PM

tobiu added parent issue #9449 on Mar 12, 2026, 7:23 PM

tobiu cross-referenced by #9449 on Mar 12, 2026, 7:24 PM

tobiu assigned to @tobiu on Mar 12, 2026, 7:25 PM

tobiu changed title from Implement Thread-Agnostic Execution Mode for Connections to Connection Foundation and Parser Refactoring on Mar 12, 2026, 10:02 PM

tobiu referenced in commit 6b7f19e - "feat: Connection Foundation and Parser Refactoring (#9452) on Mar 24, 2026, 4:06 PM

tobiu Mar 24, 2026, 4:06 PM

Input from Gemini 3.1 Pro:

✦ I have extracted the fetch() network logic out of Neo.data.parser.Stream into a newly established Neo.data.connection.Stream class. The parser now expects a ReadableStream passed into its read(rawData) method.

This establishes the Neo.data.connection.Base hierarchy. The existing Fetch and Xhr connections have been updated to extend this base class and now implement a consistent read() method.

The pipeline architecture has been fortified with clear boundaries (Connection -> Parser -> Normalizer), adhering to the single responsibility principle. Tests for both the new connection and refactored parser have been updated/added and pass successfully.

tobiu closed this issue on Mar 24, 2026, 4:06 PM