What is the Neural Link?

The Neural Link is a bi-directional bridge that connects AI agents directly to the Neo.mjs runtime. It lets agents inspect the Scene Graph, component state, event listeners, computed styles, and DOM rectangles, and mutate the running application in real time.

Why is Neo.mjs called an Application Engine instead of a framework?

Neo.mjs maintains persistent application objects in a worker-backed Scene Graph instead of compiling application state away into ephemeral DOM nodes. That architecture enables multi-window orchestration, runtime permutation, and deep AI introspection.

What is Context Engineering?

Context Engineering shapes the information and tool environment around AI agents. Neo.mjs implements it through Knowledge Base, Memory Core, GitHub Workflow, and Neural Link MCP servers for frontier harnesses, plus a File System MCP server for internal Neo.ai.Agent local loops.

What is the Neo.mjs Agent OS?

The Neo.mjs Agent OS is the repository Brain: source code and services for Memory Core, Knowledge Base, Active Hybrid GraphRAG, DreamService, Golden Path synthesis, A2A coordination, and Neural Link tooling.

Frontmatter

id	9330
title	DevIndex: Apply load mask for initial Turbo Mode soft hydration
state	Closed
labels	enhancementai
assignees	tobiu
createdAt	Feb 27, 2026, 12:11 PM
updatedAt	Feb 27, 2026, 12:14 PM
githubUrl	https://github.com/neomjs/neo/issues/9330
author	tobiu
commentsCount	1
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
contentTrust
projected
quarantined	0
signals	[]
blockedBy	[]
blocking	[]
closedAt	Feb 27, 2026, 12:14 PM

DevIndex: Apply load mask for initial Turbo Mode soft hydration

Closed v12.0.0/archive-v12-0-0-chunk-4 enhancementai

tobiu commented on Feb 27, 2026, 12:11 PM

In Turbo Mode (autoInitRecords: false), the first time a filter is applied (e.g. searching by username, selecting a country, toggling the automation filter), the Store must perform a full "Soft Hydration" pass over all raw data objects (50k+ records). This synchronous operation blocks the App Worker, causing the UI to freeze momentarily without visual feedback.

Similar to the examples/grid/bigData implementation, we need to apply a non-blocking UI update pattern (setting isLoading = 'Is Loading' and yielding the thread via await this.timeout(5)) before triggering the first heavy store mutation.

This should be applied in DevIndex.view.home.MainContainerController to:

onFilterChange
onHideAutomationChange
onHireableChange

A firstFiltering boolean flag should be introduced to track and only apply the delay on the initial, most expensive pass.

tobiu Feb 27, 2026, 12:14 PM

Input from Gemini 3.1 Pro:

✦ I have implemented the loading mask in DevIndex.view.home.MainContainerController.

Added firstFiltering flag and async/await with grid.isLoading = 'Is Loading' and this.timeout(5) to:

onFilterChange

onHideAutomationChange

onHireableChange

This should provide the necessary UI feedback and thread yielding before the Store's heavy soft hydration process. Closing this ticket as the work is committed and pushed.