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	8691
title	Fix ServiceWorker Fetch Failure on Cache Quota Exceeded
state	Closed
labels	bugaicore
assignees	tobiu
createdAt	Jan 15, 2026, 2:25 PM
updatedAt	Jan 15, 2026, 2:27 PM
githubUrl	https://github.com/neomjs/neo/issues/8691
author	tobiu
commentsCount	1
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
contentTrust
projected
quarantined	0
signals	[]
blockedBy	[]
blocking	[]
closedAt	Jan 15, 2026, 2:27 PM

Fix ServiceWorker Fetch Failure on Cache Quota Exceeded

Closed v11.22.0/archive-v11-22-0-chunk-1 bugaicore

tobiu commented on Jan 15, 2026, 2:25 PM

If the Cache Storage quota is exceeded, the cache.put() call in onFetch throws an error. Currently, this error propagates up the promise chain returned to event.respondWith(), causing the successful network request to be treated as a failure by the browser. This results in broken/missing resources.

The fix is to catch errors from cache.put() and ensure the network response is returned regardless of caching success. Logging will be suppressed to avoid console noise.

tobiu Jan 15, 2026, 2:26 PM

Input from Gemini 3 Pro:

✦ I have fixed the issue where QuotaExceededError during cache.put() would cause the fetch request to fail.

Fix Implemented:

Added a .catch() block to the cache.put() call in ServiceBase.onFetch.

This ensures that if the cache is full (or any other storage error occurs), the network response is still successfully returned to the browser.

Logging is suppressed to prevent console spam.

The changes have been pushed to dev.