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	9117
title	Refactor Grid Footer Toolbar for Store Integration
state	Closed
labels	airefactoringcore
assignees	tobiu
createdAt	Feb 12, 2026, 7:54 PM
updatedAt	Feb 12, 2026, 8:11 PM
githubUrl	https://github.com/neomjs/neo/issues/9117
author	tobiu
commentsCount	1
parentIssue	9106
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Feb 12, 2026, 8:11 PM

Refactor Grid Footer Toolbar for Store Integration

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

Closed v12.0.0 airefactoringcore

tobiu commented on Feb 12, 2026, 7:54 PM

Refactor Neo.grid.footer.Toolbar to handle store integration natively.

Changes:

Promote Store Logic: Move store_ config and beforeSetStore listener management from DevIndex.view.home.StatusToolbar to Neo.grid.footer.Toolbar.
Standardize Listeners: The base class should automatically bind onStoreFilter, onStoreLoad, and onStoreProgress if they are defined on the instance.
Refactor StatusToolbar: Update StatusToolbar to rely on the inherited store management.

Benefit: This makes Neo.grid.footer.Toolbar a robust base class for any grid footer requiring store awareness (e.g., PagingToolbar, StatusBars), reducing boilerplate in subclasses.

tobiu added the ai label on Feb 12, 2026, 7:54 PM

tobiu added the refactoring label on Feb 12, 2026, 7:54 PM

tobiu added the core label on Feb 12, 2026, 7:54 PM

tobiu assigned to @tobiu on Feb 12, 2026, 7:55 PM

tobiu referenced in commit fed8bd7 - "docs: Add intent-driven JSDoc to Grid Footer Toolbar and StatusToolbar (#9117)" on Feb 12, 2026, 8:11 PM

tobiu Feb 12, 2026, 8:11 PM

Input from Gemini 3 Pro:

✦ I have refactored Neo.grid.footer.Toolbar and StatusToolbar to implement a robust, reusable store integration pattern.

Refactoring Highlights:

Neo.grid.footer.Toolbar (Base):

Added native store_ config and beforeSetStore logic.

Automatically binds to load, filter, and progress store events using the scope: me configuration pattern (cleaner than manual binding).

Handles both instantiated Store objects and config objects.

Added placeholder methods (onStoreLoad, onStoreFilter, onStoreProgress) with intent-driven JSDoc to guide future implementations.

DevIndex.view.home.StatusToolbar (Implementation):

Removed redundant store boilerplate (store_, beforeSetStore).

Simplified logic to override the base class placeholders.

Used getReference().set() for atomic, efficient updates of the progress bar.

Added comprehensive JSDoc explaining its role in visualizing progressive loading.

This establishes a solid foundation for any future grid footers (like pagination) while cleaning up the DevIndex implementation.

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

tobiu added parent issue #9106 on Feb 12, 2026, 8:11 PM