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	9114
title	DevIndex: Add Status Toolbar and Progress Indication
state	Closed
labels	enhancementai
assignees	tobiu
createdAt	Feb 12, 2026, 5:05 PM
updatedAt	Feb 12, 2026, 6:11 PM
githubUrl	https://github.com/neomjs/neo/issues/9114
author	tobiu
commentsCount	1
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Feb 12, 2026, 6:11 PM

DevIndex: Add Status Toolbar and Progress Indication

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

Closed v12.0.0 enhancementai

tobiu commented on Feb 12, 2026, 5:05 PM

Enhance Neo.grid.Container to support footerToolbar_ config, mirroring headerToolbar.
Enhance Neo.data.proxy.Stream to fire progress events (bytes loaded vs total) when Content-Length is available.
Create DevIndex.view.home.StatusToolbar containing:
- Neo.component.Progress linked to the stream proxy.
- "Visible Rows" label (moved from Controls panel).
Update DevIndex.view.home.GridContainer to use the new footer toolbar.
Remove the row count label from DevIndex.view.home.ControlsContainer.

tobiu added the enhancement label on Feb 12, 2026, 5:05 PM

tobiu added the ai label on Feb 12, 2026, 5:05 PM

tobiu assigned to @tobiu on Feb 12, 2026, 5:15 PM

tobiu referenced in commit 7d464a1 - "feat: Add StatusToolbar to DevIndex Grid with progressive streaming updates (#9114)" on Feb 12, 2026, 6:10 PM

tobiu Feb 12, 2026, 6:11 PM

Input from Gemini 3 Pro:

✦ I have completed the task.

Changes:

Framework Enhancement (Grid):

Neo.grid.Container now supports a footerToolbar config.

Added Neo.grid.footer.Toolbar base class and SCSS.

Updated Neo.grid.Container layout to vbox with flex-direction: column to correctly stack header, body, and footer.

Ensured footerToolbar receives the grid's store reference automatically.

Framework Enhancement (Data):

Neo.data.proxy.Stream now fires progress events with loaded and total bytes.

Neo.data.Store relays these progress events.

DevIndex Application:

Created DevIndex.view.home.StatusToolbar extending Neo.grid.footer.Toolbar.

This toolbar listens to the store's progress and load events to show a progress bar and a "Visible Rows" count.

Removed the static "Visible Rows" label from ControlsContainer.

Updated GridContainer to use the new StatusToolbar.

The grid now displays a sticky footer with a real-time progress bar during data streaming and a live row count.

tobiu closed this issue on Feb 12, 2026, 6:11 PM