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	8907
title	Regression: LoadMask no longer showing in Big Data Grid example
state	Closed
labels	bugairegression
assignees	tobiu
createdAt	Jan 30, 2026, 10:07 AM
updatedAt	Jan 30, 2026, 10:08 AM
githubUrl	https://github.com/neomjs/neo/issues/8907
author	tobiu
commentsCount	1
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Jan 30, 2026, 10:08 AM

Regression: LoadMask no longer showing in Big Data Grid example

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

Closed v11.24.0 bugairegression

tobiu commented on Jan 30, 2026, 10:07 AM

Description

The "Is Loading" mask in the Big Data Grid example (examples/grid/bigData) stopped appearing during heavy operations (e.g., changing "Amount Rows" or "Amount Columns").

Root Cause

Recent changes in src/mixin/VdomLifecycle.mjs introduced an await new Promise(resolve => setTimeout(resolve, 1)); inside executeVdomUpdate. This forces the VDOM update process to yield to the macrotask queue.

In examples/grid/bigData/ControlsContainer.mjs, the code sets isLoading = 'Is Loading' and immediately triggers a heavy synchronous operation (e.g., grid.store.amountRows = ...).

Because the App Worker is single-threaded, the synchronous data generation operation blocks the event loop. The setTimeout callback in executeVdomUpdate is starved until the heavy operation completes, causing the "Loading" mask update to be sent too late (after the work is already done).

Fix

Manually yield execution in ControlsContainer.mjs after setting the loading state but before triggering the heavy operation. This allows the VDOM update macrotask to run and flush the mask state to the DOM.

Impact

examples/grid/bigData/ControlsContainer.mjs

Proposed Changes

Add await me.timeout(5); in:

onAmountColumnsChange
onAmountRowsChange
onFilterFieldChange
onControlsToggleButtonClick (already present, ensuring consistency)

Verification: User has verified the fix locally.

tobiu added the bug label on Jan 30, 2026, 10:07 AM

tobiu added the ai label on Jan 30, 2026, 10:07 AM

tobiu added the regression label on Jan 30, 2026, 10:07 AM

tobiu assigned to @tobiu on Jan 30, 2026, 10:08 AM

tobiu Jan 30, 2026, 10:08 AM

Input from Gemini 3 Pro:

✦ I have applied the fix to examples/grid/bigData/ControlsContainer.mjs by introducing a me.timeout(5) yield. This ensures the VDOM update has time to dispatch the 'Loading' state before the App Worker is blocked by the heavy data generation process.

Changes committed in 0fe6cd300.

tobiu referenced in commit 0fe6cd3 - "fix: LoadMask no longer showing in Big Data Grid example (#8907)" on Jan 30, 2026, 10:08 AM

tobiu closed this issue on Jan 30, 2026, 10:08 AM