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	8498
title	ServiceWorker.preloadAssets crashes on 404s instead of handling errors gracefully
state	Closed
labels	bugaicore
assignees	tobiu
createdAt	Jan 10, 2026, 12:45 PM
updatedAt	Jan 10, 2026, 12:58 PM
githubUrl	https://github.com/neomjs/neo/issues/8498
author	tobiu
commentsCount	1
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Jan 10, 2026, 12:58 PM

ServiceWorker.preloadAssets crashes on 404s instead of handling errors gracefully

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

Closed v11.20.0 bugaicore

tobiu commented on Jan 10, 2026, 12:45 PM

The Neo.ServiceWorker.preloadAssets method fails completely if any of the requested URLs return a 404 or network error.

Current Behavior: The method uses cache.addAll(items). If any request in the list fails, cache.addAll rejects the entire promise, adding none of the files to the cache. This results in an unhandled promise rejection or a crash in the calling code.

Error:

RemoteMethodAccess.mjs:216 TypeError: Failed to execute 'addAll' on 'Cache': Request failed

Goal: Make preloadAssets more robust. It should gracefully handle failures, ideally by:

Attempting to add files.
If addAll fails (or by design), iterating and adding files individually so that valid files are cached even if one is missing.
Returning a meaningful response to the caller (e.g., {success: true, failed: ['url1', 'url2']}) instead of crashing.

Proposed Solution: Modify src/worker/ServiceBase.mjs -> preloadAssets to catch errors during fetch/cache operations and report partial successes or specific failures.

tobiu added the bug label on Jan 10, 2026, 12:45 PM

tobiu added the ai label on Jan 10, 2026, 12:45 PM

tobiu added the core label on Jan 10, 2026, 12:45 PM

tobiu assigned to @tobiu on Jan 10, 2026, 12:46 PM

tobiu referenced in commit 9508c44 - "fix: Gracefully handle 404s in ServiceWorker.preloadAssets with success ratio (#8498)" on Jan 10, 2026, 12:58 PM

tobiu Jan 10, 2026, 12:58 PM

Input from tobiu:

◆ Refactored preloadAssets to gracefully handle fetch errors (e.g., 404s) and provide detailed result metrics.

New Behavior:

No Crash: The method no longer throws/rejects if individual assets fail to load. It catches errors per file.

Strict Success: The success flag now indicates strict completion. true only if all requested files are available (pre-cached or successfully fetched). false if any file failed.

Success Ratio: Added a ratio property (0 to 1) indicating the percentage of available assets.

Detailed Reporting: Returns a failed array containing the URLs that could not be loaded.

Return Object:
{
    failed: ['https://example.com/missing.jpg'],
    ratio: 0.9, // 9/10 successful
    success: false
}
This allows developers to decide whether a partial success is acceptable for their use case.

tobiu closed this issue on Jan 10, 2026, 12:58 PM