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	9188
title	Implement Stop Stream Capability for DevIndex
state	Closed
labels	enhancementai
assignees	tobiu
createdAt	Feb 17, 2026, 12:40 AM
updatedAt	Feb 17, 2026, 1:21 AM
githubUrl	https://github.com/neomjs/neo/issues/9188
author	tobiu
commentsCount	1
parentIssue	9106
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Feb 17, 2026, 1:21 AM

Implement Stop Stream Capability for DevIndex

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

Closed v12.0.0 enhancementai

tobiu commented on Feb 17, 2026, 12:40 AM

This task implements a "Stop Stream" capability for the DevIndex application to allow users to cancel large data streams. This is a critical usability feature for users on slow or metered connections.

Objectives:

Proxy Enhancement (src/data/proxy/Stream.mjs):
- Implement an abort() method using AbortController.
- Ensure the fetch request and stream reader are properly cancelled.
- Gracefully handle the abort signal without throwing visible errors to the user (unless intended).
Store Integration (src/data/Store.mjs):
- Expose an abort() method that delegates to the active proxy.
- Ensure the store state (isLoading, isStreaming) is correctly reset upon cancellation.
UI Implementation (apps/devindex/view/home/StatusToolbar.mjs):
- Add a "Stop" button (icon: fa-stop or fa-ban) next to the progress bar.
- Bind the button's visibility to the store's loading state.
- Wire the click event to the store's abort() method.

Acceptance Criteria:

Stream.abort() successfully cancels the network request.
Store.abort() stops the loading process and resets loading flags.
The grid remains functional with the data loaded up to the point of cancellation.
A "Stop" button appears in the StatusToolbar during streaming and disappears when finished or stopped.
Clicking the "Stop" button cancels the stream immediately.

tobiu added the enhancement label on Feb 17, 2026, 12:40 AM

tobiu added the ai label on Feb 17, 2026, 12:40 AM

tobiu assigned to @tobiu on Feb 17, 2026, 12:41 AM

tobiu added parent issue #9106 on Feb 17, 2026, 12:41 AM

tobiu referenced in commit 9dd97e7 - "feat(devindex): Implement Stop Stream capability with progressive chunk sizing (#9187, #9188)" on Feb 17, 2026, 1:21 AM

tobiu Feb 17, 2026, 1:21 AM

Input from Gemini 3 Pro:

✦ I have implemented the "Stop Stream" capability.

Changes:

Proxy: Added abort() to Stream.mjs using AbortController.

Store: Exposed abort() to delegate to the proxy.

UI:

Added a "Stop" button to StatusToolbar.mjs.

Wired it to up.onStopButtonClick -> store.abort().

Styled with devindex-stop-stream-button class and red icon color (--devindex-stop-stream-button-color).

Used fa-ban for the icon to strictly signal "Abort".

The grid now allows users to cancel the data stream at any time, preserving the data loaded up to that point.

tobiu closed this issue on Feb 17, 2026, 1:21 AM

tobiu cross-referenced by #9189 on Feb 17, 2026, 1:52 AM