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	9261
title	Create Frontend Guide 3: State Management & Controls
state	Closed
labels	documentationai
assignees	tobiu
createdAt	Feb 22, 2026, 6:47 PM
updatedAt	Feb 22, 2026, 6:58 PM
githubUrl	https://github.com/neomjs/neo/issues/9261
author	tobiu
commentsCount	1
parentIssue	9257
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Feb 22, 2026, 6:58 PM

Create Frontend Guide 3: State Management & Controls

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

Closed v12.0.0 documentationai

tobiu commented on Feb 22, 2026, 6:47 PM

Objective: Explain how ControlsContainer (filters/search) binds to the Contributors store via MainContainerStateProvider.

Tasks:

Create learn/guides/devindex/frontend/StateAndControls.md.
Detail the real-time filtering and sorting of 50,000 records.
Explain how the UI avoids freezing because filtering happens in the Data/App Worker.

tobiu added the documentation label on Feb 22, 2026, 6:47 PM

tobiu added the ai label on Feb 22, 2026, 6:47 PM

tobiu assigned to @tobiu on Feb 22, 2026, 6:48 PM

tobiu added parent issue #9257 on Feb 22, 2026, 6:48 PM

tobiu referenced in commit 085cbee - "docs: Create Frontend Guide 3 (State Management & Controls) (#9261)" on Feb 22, 2026, 6:58 PM

tobiu Feb 22, 2026, 6:58 PM

Input from Gemini 3.1 Pro:

✦ I have completely rewritten the StateAndControls.md guide as requested.

Key deep-dive additions:

Explained the Neo.mjs MVC/MVVM architecture.

Detailed how the MainContainer orchestrates the UI using logical reference lookups instead of hardcoded DOM IDs.

Highlighted MainContainerStateProvider and ViewportStateProvider as decoupled data hubs for local and global state (e.g., pausing animateVisuals when isScrolling).

Deep dive into MainContainerController: how events like onFilterChange are routed, how the store filter is mutated, and how "Soft Hydration" executes over 50,000 raw objects purely in the App Worker.

Detailed the "Data Mode" toggle and how StatusToolbar dynamically recalculates totals by checking both minified keys and fallback virtual fields (store.resolveField).

The changes have been successfully committed and pushed to the remote repository. Closing this issue.

tobiu closed this issue on Feb 22, 2026, 6:58 PM

tobiu referenced in commit 6d341e3 - "docs: Create Frontend Guide 3 (State Management & Controls) (#9261)" on Feb 22, 2026, 7:21 PM